Florian Hammerschmidt
Florian Hammerschmidt
Another idea is to force print decorators on the line above the external keyword in general. ```res @decorator1 @decorator2 @decorator3 external f1: someType1 => someType2 = "someFunc" ``` I still...
Even if you were tracking the context, you'd end up with one external taking up multiple lines more often than not because of the hard 100 character limit per line....
could still be interesting
As long as we don't get rid of argument punning I am all for it.
The only difference between `%raw` and `%ffi` is that with `%ffi` the arity is checked, so it is safer and should be preferred over raw. See error in [playground](https://rescript-lang.org/try?version=v12.0.0-alpha.13&module=esmodule&code=DYUwLgBGIM5gSgQwO4C4IEsB2kC8A+THCXCAUgCcUAKAAwDMBXLAYzAwHssJEATX6gA8ANBACeuAKwBKAN4QK4RhW6CIAanEQAvrWkAofaEjQ4AMXoZ02PIRsly9S3Sat2XHvyGiJM+YrBlVQ0tXQMgA).
Maybe add a `try await` example to the tests.
It's part of [rescript-tools](https://github.com/rescript-lang/rescript-vscode/tree/master/tools#reanalyze) ``` npm install --save-dev @rescript/tools npx rescript-tools reanalyze --help ```
you need to build your project first in order to generate a `lib/bs/.sourcedirs.json`
Forgot to add that: https://rescript-lang.org/docs/manual/v12.0.0/editor-code-analysis#configuration
right, the current published tools version is 9 months old at the very least we need to publish a new tools version first or is anything else missing @zth ?