-
-
Notifications
You must be signed in to change notification settings - Fork 17
Move ranges from ArrayInterface to Static #88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I think this should be a breaking version, so that we can make it so ArrayInterface versions with ranges are incompatible with Static version with ranges. |
Codecov Report
@@ Coverage Diff @@
## master #88 +/- ##
==========================================
- Coverage 99.36% 99.09% -0.28%
==========================================
Files 2 3 +1
Lines 472 662 +190
==========================================
+ Hits 469 656 +187
- Misses 3 6 +3
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
This is complimentary to SciML/Static.jl#88 and would be a big move in disentangling static types from ArrayInterface
This replaces the concept of "canonical" integers in ArrayInterface so we can also move that functionality here.
@chriselrod and @ChrisRackauckas , this should be ready for review. |
* Remove optionally static range types This is complimentary to SciML/Static.jl#88 and would be a big move in disentangling static types from ArrayInterface * Replace CanonicalInt with Static.IntType * Remove internal `_pick_range` method
I had to manually define a bit more to get this working outside of ArrayInterface (not
known_*
traits) but it's probably better to avoid the type piracy we currently are doing withStaticInt
range constructors in downstream packaging.Solves #41