Record in list decomposed in a single step needs type hint, is this a bug?
Just noticing in multiple scenarios that the following decomposition let ({a, b}, y) = someValue gives an error the record field a can't be found, so I need to add an explicit type annotation to {a,...
View ArticleRecord in list decomposed in a single step needs type hint, is this a bug?
Can you show an example (preferrably with a playground link) where this happens? Normally if this happens when destructuring a tuple, the same thing would happen with a direct destructuring of the...
View ArticleWhat keep you guys using Rescript?
I slightly disagree. It’s not about what you can do but how you can do it. In my opinion, FP-influenced languages make code more aesthetic. Features help reduce code nestings, amount of parenthesis,...
View ArticleRecruitment on the Catala project (French)
[As the positions opening are in Paris and hosted at the French National Research Center in Computer Science INRIA, the rest of the post is in French] Bonjour à toutes et à tous, Le projet Catala...
View ArticleWhat keep you guys using Rescript?
That is the reason why i keep using rescript. The biggest problem i think in rescript is the ide support, especially in native Windows environment.
View ArticleWhat keep you guys using Rescript?
mishaszu: (TS only) typescript theoretically supports tuples but the syntax is almost identical with arrays which causes a lot of trouble The biggest pain is that TS has no idea of how to type a tuple...
View Articlegetting Fatal error: exception File "bsb_pkg_types.ml" no solution found
I am using a github repo inside another github repo. The name of first repo is FusionKit and it has multiple packages created using lerna and pnpm workspaces. The second repo is named Service and it...
View Articlegetting Fatal error: exception File "bsb_pkg_types.ml" no solution found
I think @fusionkit as a name won’t work, it needs to be "@npmNamespace/packageName" or "packageName"
View ArticleRecord in list decomposed in a single step needs type hint, is this a bug?
Hi tsnobip, thanks for your reply! I did a minimal version to demonstrate the issue:...
View ArticleWhy the function call in pipe expression needs to wrap parentheses now?
module Codec = { type encode<'v> = 'v => Js.Json.t type decode<'v> = Js.Json.t => result<'v, exn> type t<'v> = { encode: encode<'v>, decode: decode<'v>, } let...
View ArticleWhy the function call in pipe expression needs to wrap parentheses now?
Mng12345: let encode = codec => codec.encode Because it’s uncurried. If you change the code to it won’t be needed: let encode = (codec, value) => codec.encode(value)
View ArticleWhy the function call in pipe expression needs to wrap parentheses now?
I thought the pipe operator can automatically recognize and handle this situtation.
View ArticleWhy the function call in pipe expression needs to wrap parentheses now?
There are a lot of libraries need to modify their code to upgrade to v11…
View ArticleWhy the function call in pipe expression needs to wrap parentheses now?
Could you share a list?
View ArticleWhy the function call in pipe expression needs to wrap parentheses now?
I do not have the list, i just thought the new version of the pipe might cause these changes.
View ArticleWhy the function call in pipe expression needs to wrap parentheses now?
It’s not really a pipe, it’s more about uncurried mode.
View ArticleRecord in list decomposed in a single step needs type hint, is this a bug?
to be honest I don’t understand how the first example can even compile: let doIt = () => { // compiles let (x, y) = Definition.getList() let {a, b} = x } given it wouldn’t compile when not inside a...
View ArticleRecord in list decomposed in a single step needs type hint, is this a bug?
Amazing discoveries. And even this does not compile outside of the function. But it does inside: // breaks let {a, b} = Definition.getRecord() let doIt = () => { // compiles let {a, b} =...
View Article[ANN] rescript-edgedb - Use EdgeDB with full type safety in ReScript
There’s now a blog post (written by me) published on EdgeDB’s blog about the ReScript + EdgeDB integration and experience: ReScript and EdgeDB | EdgeDB Blog
View Article