Experiment: use JSDoc types in JS runtime #1218
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.


Most of the contents are scaffolding, what this really adds is:
libraries/js/effekt_*.jsusing the JSDoc syntax// @ts-checkcomment at the top of the fileThis means that we get some light form of type checking when investigating the JS output in VSCode.
It's especially useful when writing FFI. :)
I have not tested this properly, I really only tried it on two examples.
To me, this is just a first step: the type annotations currently present are a combination of my own vibes and of Claude's ideas of what the types should be. There's also a lot of
@ts-ignorecomments and casts toanyand similar things to make TS shut up, this could likely be much more improved, hence the draft status of this PR.