Reason 3.1.0 Released


#1

#2

Suggestion for HISTORY.md: add dates to version numbers, turn issue/pull request numbers into links (automated via a regex?)


#3

Awesome, btw is vscode-reasonml coordinated with this release? I mean will it understand and highlight the new syntaxes?


#4

It’s not; is it badly affected by it?


#5

Actually I haven’t tried it, was just checking :slight_smile: I’ll try it out this weekend and report back.


#6

Inline comment is current broken.


#7

@rauschma links now added. @thangngoc89 feel free to discuss in PM


#8

New pipe sugar allows inserting argument at arbitrary position: [1, 2, 3] |> map(, a => a + 1) |> keep(, a => a === 2). Basically ES2030.

This example is not very clear. Not being an expert, I feel lost. Why is this significant… Why ES2030?


#9

See https://github.com/tc39/proposal-pipeline-operator#usage-with--partial-application-syntax


#10

Thanks for the excellent work, I am loving everything I do with Reason more than any other programming language (the professor of my cryptology class was even kind enough to allow me to use Reason for our assignments which has been fantastic). The let%extension and new pipeline syntax are super exciting :grinning:
Will 3.1.0 get an OPAM release?


#11

Hi @gandulio We just need to clean up and fix some of the release scripts in the Reason repo since we refactored rtop into its own package. Help is appreciated.


#12

Thanks for the hard work! Super excited about the new pipe syntax and trailing commas.

On a related note, could someone enlighten me what the “let%foo extension sugar” is about?


#13

IT’s a sugar syntax for ppx let https://github.com/janestreet/ppx_let


#14

Have you tried it so far btw?


#15

No. But I already see the impact on my current code

Before:

[%raw "foo.js"];

after

%raw "foo.js";

#16

@jordwalke Any suggestions for where to start with the release scripts? I may be able to offer a little help.


#17

I’m finding a lot of syntax weirdness with VSCode. It will often say my code is incorrect even when it compiles fine, and syntax highlighting can get weird in places.

Is there a timeline for when it will be updated to the new syntax changes?

edit: I can provide more details on the weirdness tomorrow if needed.


#18

You might be seeing error messages from a slightly older version of Merlin? Can you check if you upgraded to the latest version of reason-cli?


#19

Forgot to upgrade reason-cli, so I did that now.

I’m still getting weird syntax errors:

It compiles fine, and seems to infer types correctly, but there (and in other spots) is giving me a [merlin] Uninterpreted extension 'bs.obj'. error. It also doesn’t highlight syntax within the module correctly.


#20

Reason 3.1.0 requires bs-platform@2.2.2 . Do you have the correct version?