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
Declaring ranges in vectors creates type instabilities (which show up as false positives on JET.jl), besides feeling a bit weird and encouraging bad habits (using vectors for a small collection of heterogenous types). I assume it doesn't have much of an effect on performance here (or else it wouldn't be used), but would it make sense to at least allow users to pass tuples instead of vectors?
The text was updated successfully, but these errors were encountered:
I find it hard to imagine a use-case where the performance improvement of tuples is worth a breaking change. No objection to allowing tuples. PR welcome.
Declaring ranges in vectors creates type instabilities (which show up as false positives on JET.jl), besides feeling a bit weird and encouraging bad habits (using vectors for a small collection of heterogenous types). I assume it doesn't have much of an effect on performance here (or else it wouldn't be used), but would it make sense to at least allow users to pass tuples instead of vectors?
The text was updated successfully, but these errors were encountered: