Don’t clear symbols when forwarding lapack

[christiangnrd]

I went with the approach of changing the default value in load_accelerate.

@ViralBShah Should we be passing in the clear kwarg to both calls to forward_accelerate?

AppleAccelerate.jl/src/AppleAccelerate.jl

Lines 51 to 54 in b12ceba

	forward_accelerate(:lp64; new_lapack=true, clear, verbose)
	if load_ilp64
	forward_accelerate(:ilp64; new_lapack=true, verbose)
	end

Fix #78

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.73%. Comparing base (b12ceba) to head (c67fa49).
Report is 3 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #82      +/-   ##
==========================================
+ Coverage   73.22%   75.73%   +2.51%     
==========================================
  Files           4        4              
  Lines         239      239              
==========================================
+ Hits          175      181       +6     
+ Misses         64       58       -6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ViralBShah]

The default for clear is false. So not necessarily, but also no harm.

Let's add a comment on why we are doing this. Basically, not clearing the forwards means BLAS/LAPACK bindings will forward to openblas unless overwrriten by bindings in Accelerate. So this way gemmt will go to openblas.

[christiangnrd]

Should be good to go.

[ViralBShah]

Released this in a new version. Needed various other updates for the registry URL and TagBot which are all done too.