Paul Tsnobiladzé

create-rescript-app now defaults to `.res.mjs` so this should not happen anymore.

Int in ReScript is meant to be 32 bits, so `Belt.Int.fromString` is unsafe compared to `RescriptCore.Int.fromString` because it doesn't check for that. If something has to be corrected, it is...

this could be simplified with v11 thanks to the new representation of untagged variants that will allow `Nullable.t` to be defined like this: ```res module Nullable = { @unboxed type...

yeah I agree, those utility functions can come handy from time to time (eg as a parameter of a filter function).

I'm closing this for now, we'll revisit if there's some interest once v12 is released and Core is used by default.

> And this if you want it to be called `getExnWithMessage`. I think this name is more coherent with the other functions, could also be called `getExnWithMsg` to make it...

You can even simplify it down to [this](https://rescript-lang.org/try?version=v11.1.0&code=LYewJgrgNgpgBAISgQwFxwN4Cg51gFzmQCdjkBPdACgHJk4BeAPjhoCMAaOAKQGcA6AIKkK-fAB46TAJSMWfISPJjJbJlgC+jTDjwxCJMuW1UYAOwDG4GMS6HZzHgOFH+wZAAdTl67aKlpTSwgA): ```res module Bla: { let array: ('a => 'b, Js.Array.t } = { let array = (encoder, arr) => Js.Array.map(encoder, arr) }...

> Version: rescript 11.1.0-rc.3 > > The non-existed function is not highlighted and there's no location in the compilation error as well. Hmm yes error location is pretty bad right...

I think that genType got fixed with rescript-lang/rescript/pull/7285, can you confirm @cknitt @zth ?

good catch @samwightt! We'll look into it before v12.