-
Notifications
You must be signed in to change notification settings - Fork 39
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
deprecate RecursiveVec, improve x0 initialisation for GPU (#97)
* cleanup and deprecate recursivevec * make x0 initialisation GPU compatible * update CI and reduce number of combinations * remove erroneous files * remove todo Co-authored-by: Lukas Devos <[email protected]> * fix docs and tests for recursivevec removal * remove unused code block * keep RecursiveVec in tests for deprecations * actually add deprecated.jl --------- Co-authored-by: Lukas Devos <[email protected]>
- Loading branch information
Showing
17 changed files
with
51 additions
and
176 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
Base.@deprecate(RecursiveVec(args...), tuple(args...)) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
e6b1fee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since you deprecate RecursiveVec, is there a simple struct (not AbstractVector) which implements your vector interface in order to test it?
e6b1fee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes there is a
MinimalVec
type defined in "test/testsetup.jl" which can be controlled to allow in-place operations or only support out-of-place operations with a type parameter. It is however not part of the package itself and thus not meant to be used. I was wondering if deprecatingRecursiveVec
would constitute a breaking change and should thus yield version 0.9, but @lkdvos found a reference stating that deprecating a structure or method can happen in an non-breaking version update.Is there any functionality that you miss or doesn't work from replacing
RecursiveVec
with aVector
orTuple
of its constituents?e6b1fee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have to say that in the meantime I have come to regret making that call. MPSKit also broke because of this, as we were using RecursiveVec to dispatch on.
I wouldn't be opposed to adding
MinimalVec
to VectorInterface as testing utilitye6b1fee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I adopt VI in BifurcationKit. Having a simple vector example implementing the interface is nice to test against because if I use an
AbstractArray
as a test, it wont be satisfying.e6b1fee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is a valid question indeed. Maybe we can move our
MinimalVec
implementation to VectorInterface.jl; what do you think @lkdvos ?