Conversation
tlively
approved these changes
Jul 9, 2026
Member
|
LGTM, but I wonder if there are any limits an implementation could think up that we would push back on. Maybe we should give up on this being an exhaustive list? |
Member
Author
|
Good question. In a way, I see this list less as a boundary for implementors, but more as a warning for producers: these are the values not to get excessive with individually, even if an overall module can still be fairly large. More importantly, it is the list of things that some ecosystems might want to make concrete, like the JS-API does. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Some oversights (e.g., number of active handlers) and some motivated by SpaceWasm. I don't consider any of them controversial.