wast function type name desugaring is changing in spec:301 #654
Conversation
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
kripken
force-pushed
the
spec-301
branch
4 times, most recently
from
7394a09 to
4e8af9d
Compare
|
The appveyor CI is not working well, e.g. this. It queues for very long, and then errors on something not related to this PR. cc @jasonwilliams200OK So I am inclined to merge this and not wait on figuring out the appveyor issue? Any concerns? |
|
Looks like no objections, so merging. We'll figure out the appveyor thing later (or maybe it'll fix itself?). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Update spec tests, and a fix for the desugaring change, cherry-picked from
spec-updatesbranch.