Mateusz Baran

I'm not sure, in any case I wouldn't mix CI benchmarks and benchmarks that compare different libraries.

I don't really like `SA` either. I wouldn't make any formal deprecation but I think rewriting README.md to promote `@SArray`/`@MArray` as the primary convenient way of making static arrays is...

Yes, `StaticArrays.Dynamic()` is quite unfortunate. I'll think about this.

To me it looks like all of them should be static, so it's just a matter of adding more methods to `*`.

`HybridArray(n1,n2,...)` looks quite nice, my only issue is that is would be quite unusual re-use of a type constructor. Maybe `hybrid_array(n1,n2,...)(wrapped_array)` would be better?

IIRC there was some problem with using colon there but I may be wrong. I'll try that soon.

OK, now I see what the problem is: `Size` struct in StaticArrays.jl only accepts integers and `Dynamic()`, and thus I'd have to get rid of every single usage of that...

I think it's a general Julia problem with allocation of mutable variables on stack: sometimes Julia can do that, and sometimes it can't, it's not reliable.

Weirdly enough, `a = lu(SizedMatrix{N,N}(randn(N, N))); a` works fine.

I checked again in a clean environment. `a = lu(SizedMatrix{N,N}(randn(N, N))); a` works fine on Julia 1.7.1 but not on Julia 1.8-rc1. Still weird.