You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 9, 2018. It is now read-only.
The order of fields in structs like Vector or General should follow the order in which they typically appear in a function call. This would make more natural and easier to understand calls with inline declarations with unnamed fields. For example, in case of Vector and Dscal:
native.Implementation{}.Dscal(n, scale, x, 1)
vs.
blas64.Scal(n, scale, blas64.Vector{1, x})
Similarly for General and other types.
The text was updated successfully, but these errors were encountered:
The order of fields in structs like Vector or General should follow the order in which they typically appear in a function call. This would make more natural and easier to understand calls with inline declarations with unnamed fields. For example, in case of Vector and Dscal:
Similarly for General and other types.
The text was updated successfully, but these errors were encountered: