-
Notifications
You must be signed in to change notification settings - Fork 20
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
hcat and vcat don't behave like arrays #164
Comments
@stevengj Not sure if you saw #159? I realize there are good reasons for using FIxedSizeArrays (including backward compatibility, integration into other packages, etc), and don't want to steal thunder from @SimonDanisch for this awesome package, but I wanted to mention that the issues you raised today are not present in StaticArrays.jl. |
@andyferris, thanks for the tip. I have to admit that the variety of packages for fixed-size arrays (FixedSizeArrays, ImmutableArrays, StaticArrays) confuses me, and I was unclear on which one I should use. I'll take a look at StaticArrays. |
No worries. There was a suggestion to add note to the READMEs of these packages which might help with this. |
Sorry about this, that's my fault. I just don't feel comfortable about spreading the deprecation of FixedSizeArrays before I haven't actually moved away my own packages! |
Sounds good. 😃 I'm currently making a few architectural changes to StaticArrays and will tag a new minor release when that is in reasonable shape (a couple of days) so we can time it with that. On a related note, how are you finding using StaticArrays for geometry? Did you get a |
I don't actually care much about the distinction between |
I look forward to it! 😄 |
I was expecting that
Vec
would behave like anArray
here, i.e. thathcat
would produce aMat{2,2}
andvcat
would produce aVec{4}
.The text was updated successfully, but these errors were encountered: