Add non-normative section for flex-event specification #890
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
|
What is the relation between this and #789? Are we going to land these piecemeal or do you want to keep it in a PR while it is fleshed out? |
That PR seems to be abandoned, but regardless, I think some amount of iterative work will be required due to the sheer size of the proposal. I will add a few more substantive commits to this PR before merging, with the caveat that there will be a number of inline issues about integers vs strings and integer sizes, and I would still like #856 to land first. |
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 would add even more definitions here for the trigger spec structure itself, but a lot of that is dependent on choices for fixed-width arithmetic and reusing parts of #856.
Preview | Diff