Michel Hermier

It would make things more functional style, but it is the more extensible sugar syntax I can think of. In extra, if that as importance or extra usage, it would...

`|` was chosen as a mix match of the `|>` operator and the `@` operator used for composition in some language. While I'm happy with it, we can discuss the...

At usage, it would definitively be equivalent. The operator has to be accepted or changed, but it gives an extra reason to have that language construction.

@PureFox48 Can you describe operator precedence in terms of *between* operators? Expressing in terms of numbers is not really clear, and might change with possible additions.

I also always struggle with these questions. I updated the priority to be in par with the JS pipeline. My main question was about the `?:`, and it appears that...

Looking at the JS paper, the placeholder operator seems overkill (introduce too much complexity in the compiler). Instead, I propose that we can guarantee that we can put at minimum...

Well since there is no chain going further, I didn't thought more about it. For me it does return `null` as a way to terminate the chain. But the fact,...

As long as we can pass 1 argument we can passe any argument, using the following trick: ```javascript class Apply { construct new(fn) { _fn = fn } call(args) {...

It is, I tested with main branch and it doesn't seems to trigger the issue anymore. I suspect the stack error can still occurs if a foreign function triggers a...

Fixed with #1124. With a new fresh view, I found it pretty quickly. The `ObjFn::arity` was not used in `wrenCallFunction` resulting in approximative `ObjFiber::stackTop` adjustments. Fixing that exposed an secondary...