Sean T Allen

Is having an annotation that will cause a compiler error if an optimization isn't applied an alternative?

> I'm not sure I understand what "when this feature will succeed and when it won't" means. The RFC says "The value of a static array literal can only be...

>"The value of a static array literal can only be `Array[T] val`, where `T` is a floating-point or integral numeric type." What specifically would the check be that the compiler...

> If you tried to do `let foo: Array[U32] ref = #[1;2]` the compiler would say "right side must be a subtype of left side; Array[U32 val] val is not...

> If you tried to do `let foo: Array[U32] ref = #[1;2]` the compiler would say "right side must be a subtype of left side; Array[U32 val] val is not...

If this was done as an optimization, could we not have more types that could play, so you could for example, create Maps that could be optimized as such without...

We discussed this during the sync call https://sync-recordings.ponylang.io/r/2023_04_25.m4a. In general, Joe is in favor. I am still against. I raised by concerns for things I would want to see addressed...

@mfelsche noted to me after the sync call that he has some thoughts on adding SIMD support to Pony that he sees as related to this RFC and would like...

> Can we have a generic static array definition like > class Foo[A: UnsignedInteger[A] val = USize] > let a: Array[A] = #[1; 2; 3] Without compile time expression support,...

> Why only arrays? I think there could be a relation to introducing let fields in primitive too. primitives don't have fields, did you mean, primitives that are let fields...