Updates for v3 RTM #1739
Merged
Updates for v3 RTM #1739
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
sebastienros
approved these changes
Jan 19, 2024
|
As @sebastienros basically gave us the go-live license, why not 🚀 |
|
Do you think your unfinished generators PR is not worth it in its current state. As in better not do anything than not support all quircks? |
|
I think it can wait. Basically it suffers from the problem that it's now impossible from resume from expression state. Statements are easier now when it's just part of a list, but expressions are inside of a complex AST tree. The public APIs won't be affected from this when/if implemented. |
|
This is what you get from releasing Duke Nukem projects
|
scgm0
pushed a commit
to scgm0/jint
that referenced
this pull request
Jan 25, 2024
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.
As generators and tweaks seem to be a forever project, might be easier to finally release the v3. I've gone through API from consuming viewpoint and I think it's quite near of not exposing too much and allows wiggle room in development - and there's always v4...
A week or so to ensure latest release doesn't break too much, or a year.. maybe.