feat: add type annotations #565
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
delphinus
force-pushed
the
feat/types
branch
17 times, most recently
from
b8789ab
to
c7fc90f
Compare
delphinus
force-pushed
the
feat/types
branch
3 times, most recently
from
832687b
to
c341a8a
Compare
|
Consider using type stubs from https://github.com/LuaCATS/busted and https://github.com/LuaCATS/luassert |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I'm adding type annotations and some documentations for plenary. At first, I have added to
plenary.pathbecause this is the most popular module here, I think.TODO
bitalready exists in LuaJIT)plenary.async.uvshould be generated by scripts.plenary.async.asyncshould also be generated 🤔