Clik here to view.
Missing type annotation from generated interface file
github.com/rescript-lang/rescript-vscode Wrong type annotation generated in the interface file opened 02:24PM - 20 Feb 24 UTC soundstep Original discussion:...
View ArticleType duplication between interface file and implementation
Interesting, thanks for the reply, I’ll try that!
View ArticleWhat's the current view on PPX usage?
I use them quite a bit and they feel pretty stable to me. It would negatively impact my usage of the language if they went away. As far as I am aware they are here to stay.
View ArticleClik here to view.
Printing PPX'd source with ReScript
AFACIT there’s no way to print generated code from rescript sources, so I came up with the following workflow. Context I have a few ppx’s to update to v11. I didn’t touch them for years, so I’m rusty...
View ArticleQuick migration guide to uncurried mode for PPX maintainers?
Thanks, I will look into those! Also, the workflow that I’m using right now for migration.
View ArticleClik here to view.
What's the current view on PPX usage?
I made it about a year ago. Things got a bit worse since then
View ArticleClik here to view.
@call decorator for callable objects?
I notice that vitest allows you to extend your test function with skipIf, only, each, etc: vitest.dev Vitest Next generation testing framework powered by Vite import { assert, test } from 'vitest'...
View Article@call decorator for callable objects?
skipIf doesnt change the signature of the function but other examples do: extend/each and not all functions of that signature will have the properties to do the decoration either.
View Article@call decorator for callable objects?
This is what I did in rescript-bun - a regular describe function, and a Describe module with skipIf: https://github.com/zth/rescript-bun/blob/main/src/Test.res#L53-L105 describe("whatever", () => {...
View Article@call decorator for callable objects?
Ah Yeah, i have that in my current version. In the latest vitest it looks like these can change the signature of the called function: test.each([ { a: 1, b: 1, expected: 2 }, { a: 1, b: 2, expected: 3...
View ArticlePrinting PPX'd source with ReScript
Yeah great write up @alex.fedoseev ! Ideally the rescript bin should also be able to print the PPXed code. No idea if that’d be hard to implement though.
View ArticleWhat's the current view on PPX usage?
I don’t think anything has changed really in the stance towards PPXes - they’re still discouraged in general because of their complexity, maintenance burden etc. They also tend to be quite buggy,...
View Article@call decorator for callable objects?
I would still say that you can enforce an order, you can say that you should always use skipIf first and not after the functions that change the signature, like each. You’d have to define different...
View ArticleQuick migration guide to uncurried mode for PPX maintainers?
So far, the changes I had to make to build examples with the updated ppx can be summarized as follows: let f = @res.arity(2) (a, b) => a + b // annotate function definitions let x = @res.uapp f(1,...
View Article"Not sure what to do with this character" error when using a German umlaut in...
type mustard = Dijon | Wholegrain | Düsseldorf does give an error (“Not sure what to do with this character”). I tried escaping the identifier but to no avail (“Did you mean `Düsseldorf` instead of...
View Article"Not sure what to do with this character" error when using a German umlaut in...
identifiers can only use ascii characters, if you want to use any utf8 characters, use @as: type mustard = | Dijon | Wholegrained | @as("Düsseldorf") Dusseldorf
View Article[ANN] ReScript Core 1.1.0 is out
ReScript Core 1.1.0 (and 1.0.0 which was released a while back) has been released. Until Core is integrated into the compiler (v12 likely), versioning will work this way: 0.x (currently 0.7.0) will...
View Article