Gordon Tisher
Gordon Tisher
Looking
Luke's work uses syntax like `#(1+2)` to denote compile-time expressions. I thought that `#([1;2])` seemed noisy, which is why I suggest `#[1;2]`. Bringing in Luke's work would not break anything...
It's a very minor subset of compile-time expressions. Luke's work involves implementing an interpreter in the compiler that can evaluate expressions (including constructing objects and calling their methods). This PR...
The "Alternatives" section addresses the "just optimization" option. If I'm implementing an algorithm that requires static data for performance reasons, I want to explicitly know that it's going to be...
If someone tries to declare a `ref` or `iso` static array, the compiler will tell them they can't do that. If we make this "just an optimization", their code will...
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 `Array[T]...
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 a...
`#[]` means point a val array to a static section of data. Allowing arbitrary object types would mean interpreting them at compile-time and then serializing them into the binary.
Thanks @SeanTAllen, 1.7.1 seems to work for me on Windows.
Unfortunately no.