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
It is not entirely clear to me if the extensions for LinearAlgebra belong in a package extension, or should just be a part (possibly submodule) of the main module. For now, it would be loaded by default anyways, as LinearAlgebra is still an stdlib that is always included, but it looks like that might not always be the case in the future.
On the other hand, there is probably a large part of the package that actually does depend on implementations in LinearAlgebra, so I would guess that just having this in the main package is the best way forwards, considering that in typical usecases, projects will have LinearAlgebra loaded one way or another.
The text was updated successfully, but these errors were encountered:
I think I was just undecided about that so for the sake of keeping the option open of creating a package extension I organized it in that way to make the dependency structure of the codebase clearer.
It is not entirely clear to me if the extensions for LinearAlgebra belong in a package extension, or should just be a part (possibly submodule) of the main module. For now, it would be loaded by default anyways, as LinearAlgebra is still an stdlib that is always included, but it looks like that might not always be the case in the future.
On the other hand, there is probably a large part of the package that actually does depend on implementations in LinearAlgebra, so I would guess that just having this in the main package is the best way forwards, considering that in typical usecases, projects will have LinearAlgebra loaded one way or another.
The text was updated successfully, but these errors were encountered: