This repository has been archived by the owner on Mar 12, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CuArrays/GPUArrays currently define lots of constructors (and methods of
similar
andconvert
) that have diverged from Base and really should not exist. This PR tries to get rid of them, to improve maintainability and code portability.As part of that work, I propose to move essential functionality such as constructors to the concrete packages (ie. CuArrays). Defining these methods in a generic fashion is cumbersome, introduces loads of ambiguities, and results in applicable but nonsensical method invocations. For example:
This because of a generic
Base.convert(::Type{<: GPUArray{T1}}, ...)
that is only defined to be invoked on concrete subtypes. Base doesn't attempt to share such functionality between Array and AbstractArray.Obviously massively breaking, but seems to pass tests except for some CUSOLVER failure.