Benoit Giannangeli

Ranges are syntaxic sugar to create list of integers. But when used in a `foreach` statement it should be expanded to a classic `for` statement: ```buzz foreach (int i in...

Error stack is lost when a function is JIT compiled

1

To reproduce: - `zig build -Djit_always_on` - `buzz -t tests/compile_errors/008-error-message.buzz`

Remove implicit `this` argument

4

Since buzz is supposed to be _unambiguous_ do we need implicit `this` argument for objects' methods? ```buzz object Person { str name, fun sayHello(str to) -> print("Hello {to} from {this.name}");...

Field access doesn't need to rely on a name lookup at runtime. It could be an index generated at compile time juste like we do for locals.

Right now std lib errors matches zig errors, most of them are too low-level for buzz: - [ ] Regroup errors that are too fine-grained for buzz - [ ]...

Either declare an object as immutable: ```buzz immut object Point { int x, int y, } ``` And/Or declare an instance as immutable: ```buzz immut Point point = Point{ x...

Immutability by default

2

Should things be immutable (and private) by default? ```buzz str hello = "hello"; hello = "bye"; | fails var str hello = "hello"; hello = "bye"; | ok ```

```bash $ buzz --dump myscript.buzz myscript.out $ buzz myscript.out ``` Implies we know how to serialize any buzz data since chunk embark constants.

Use [std.Thread](https://ziglang.org/documentation/master/std/#A;std:Thread) - [x] Thread - [x] Mutex - [x] Semaphore - [ ] Thread safety

This is maybe to high level for buzz. ```buzz typedef number = ; fun compare(number a, number b) > bool { | ... } ```