RFC: Nested record definitions
Real types, with autogenerated names that aren’t possible to reference unless using escaped identifiers (a reminder that you should probably break it out to a real type definition if you want to reuse...
View ArticleRFC: Nested record definitions
Yeah I lean towards that as well - make it a concrete definition if you need reuse. We can make the tooling make it super easy to extract to a concrete definition.
View ArticleRFC: Nested record definitions
Would nested variants be a stretch or do you want to keep this scoped to records?
View ArticleRFC: Nested record definitions
Definitely not ruling out that, but we should start with records and see how that’s used. Variants are slightly different because of things like @unboxed and @tag where you often want/need to...
View ArticleClik here to view.
RFC: Nested record definitions
I’m a little bit skeptic about using the @as attribute for renaming the underline types. zth: type options = { startFrom: float, persist?: @as("persistOptions") { // makes the type `type...
View ArticleClik here to view.
Error in ReScript Template
I ran the npm command to create the default ReScript Vite app installed the extension npm run res:dev npm run dev And I get the error bellow, everything still runs fine, it seems to be only inside of...
View ArticleError in ReScript Template
Can you share the rescript.json file? Have you used the command before? And did you do it with @latest like npm create rescript-app@latest?
View ArticleError in ReScript Template
hello, yes I did exactly with that command, everything untouched, same with the rescript.json fille, original from the template. Vite 5 template with react, all latest versions 11.1.4 rescript and...
View ArticleReading a file contents
I wonder if I missed something. I was a bit bummed that I had to write all that to read the contents of a file (and figure out how as I could not find an example in the docs!): type blob @send...
View ArticleReading a file contents
Much like Typescript, ReScript doesn’t necessarily target node; because of this, the docs try to be agnostic as to the runtime. Instead, the bindings to node are provided as a library, available here....
View ArticleError in ReScript Template
I’ve noticed VSCode language extensions intermittently bug out all the time (not just rescript, typescript too). If I see an issue in the editor but the command line shows okay, you can try restarting...
View ArticleError in ReScript Template
I’ve done that a few times toto, unfortunately not the solution, but thanks
View ArticleError in ReScript Template
Is this happening all the time, even if you restart the editor? About having to restart the LS: Language servers are tricky, but we’d still like to eliminate as many problems as we can. So please...
View ArticleError in ReScript Template
Could you open an issue on the vscode extension tracker? So we can debug it from there.
View ArticleReading a file contents
That’s great, thank you. I did not think of looking for NodeJs bindings. The website only mentions React bindings.
View ArticleReading a file contents
Yeah, I’d imagine that’s because the React bindings are maintained by the ReScript team, whereas the NodeJs bindings are a third party library.
View ArticleReact 19 and ReScript
Hello everybody, I’m considering upgrading to React 19, I was wondering if anybody tried React 19 with ReScript and had any feedback about it. Are there still some blockers?
View ArticleApplying good ideas to Rescript documentation
This is now implemented: LLMs | ReScript Language Manual
View ArticleReact 19 and ReScript
I haven’t used React 19 yet, but if anyone has experimented with the new React compiler, I would love to hear your experiences. I looked into this a while ago, and there were some limitations, so I’m...
View Article