Benoit Giannangeli
Benoit Giannangeli
Right now if a fiber fails, we can only handle errors at the fiber creation site. Allow to handle error on any `resume` or `resolve`: ```buzz fun count(num n) >...
Right now the stack is a fixed array of 100 000 elements. - Detect when stack is overflowed - If under a high limit (lua is 1 000 000), realloc...
All my mp3s have the cover image in their metadata but kmbmpdc doesn't retrieve them.
I'm trying to build MIR with my build.zig for buzz so that users are not required to build it separately by hand and also for it to be automatically built...
There's not bitwise `MIR_NOT` instruction
closes #173
Not really useful in an object declaration since we can self reference there, but useful in protocols where we want to reference the actual object type. ```buzz protocol Clonable {...
- We already have an available tag for errors in `Value` - The parsing and type checking would not be impacted - **We could get rid of `setjmp`/`longjmp`** - Throwing...
Right now we do constant folding in specific locations. We could systematically check if a node is constant before generating it. BUT it requires to separate type checking in their...
Either create a new `builtin` lib always loaded, or always load `std`. This would allow buzz to count on the fact that some basic things are here (like https://github.com/buzz-language/buzz/issues/250)