-
Notifications
You must be signed in to change notification settings - Fork 2
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
Naming and composability? #1
Comments
Thank you! I didn't dare publicly ask for a better name (http://goo.gl/mV9MvD) , and "Flexible" was just the best thing with which I could come up. I don't like the name myself either. Much of the generated code depends on which dimensions have a fixed size and which don't, and which dimensions have a fixed lower bound and which don't. (It's flexible in this respect!) So the array length might or might not be fixed. The particular use case I needed was an array where all lower bounds are I looked at FixedSizeArrays and ImmutableArrays. Both are similar to FlexibleArrays, in the case of arrays with a fixed length. FixedSizeArrays seems to allow arbitrary choices for the underlying type -- a very neat idea, if the array length is fixed. So maybe |
I hadn't properly appreciated just how flexible this all is, and I certainly shouldn't comment on implementation without understanding it better! |
Wait... I really don't like the current name, do you have a suggestion? |
Maybe |
Or |
Leftover from JuliaLang/julia#15648 (comment).
Clearly I'm late for bikeshedding the name, but I'm not sure that name conveys the way in which they are flexible...I keep thinking of wobbly windows! I do think
OffsetArrays
is a better name, and wonder whether you could combine forces?More importantly, this seems to combine the functionality of
OffsetArrays
andFixedSizeArrays
. IfOffsetArrays
were implemented as a thin-wrapper around an arbitrary array type, wouldn't this be more composable?The text was updated successfully, but these errors were encountered: