Latest syntax

[cristianoc]

No description provided.

[cristianoc]

@mattdamon108 is there anything pending for another 10.1 release?
CC @cknitt

[mununki]

@mattdamon108 is there anything pending for another 10.1 release? CC @cknitt

I have nothing in my hand for 10.1 now.

[mununki]

I'm very excited about releasing 10.1

[cknitt]

@mattdamon108 I am excited, too! 😃

What is still open is rescript-lang/syntax#686. The current behavior is quite unintuitive, and other people have stumbled upon it too while testing the release, see cristianoc/rescript-compiler-experiments#1 (comment).

Not sure how easy this is to resolve and if it should better be tackled in a 10.1.1 or something.

[cristianoc]

@mattdamon108 I am excited, too! 😃

What is still open is rescript-lang/syntax#686. The current behavior is quite unintuitive, and other people have stumbled upon it too while testing the release, see cristianoc/rescript-compiler-experiments#1 (comment).

Not sure how easy this is to resolve and if it should better be tackled in a 10.1.1 or something.

Either way is possible. In any case one more round of testing is required to check there are no unknown issues left (or newly introduced).

[d4h0]

What is still open is rescript-lang/syntax#686. The current behavior is quite unintuitive

As excited as I am for async/await finally landing in ReScript, I 100 % agree with that. I'm pretty sure that a significant amount of people will stumble upon this.

It would be better to wait a few additional days/weeks until that issue is solved.

[cristianoc]

Periodic reminder that the issue is about pipe not async/await per se and likely that the change will be a breaking change for pipe.
Just so all elements are considered.

[cristianoc]

It's one more reason to go find out. Just, the outcome is not completely clear at this stage.

[cknitt]

I think this should also be resolved before the 10.1 release: rescript-lang/rescript-vscode#617