Skip to content

Generalize test in prep for binaryen#2510 #10011

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 12, 2019

Conversation

tlively
Copy link
Member

@tlively tlively commented Dec 11, 2019

This test unnecessarily checked for the presence of an explicit type
in a function definition in a .wast. The upcoming WebAssembly/binaryen#2510
removes this type from wast output, so this test needed to be updated first to
keep the rollers happy.

This test unnecessarily checked for the presence of an explicit type
in a function definition in a .wast. The upcoming PR emscripten-core#2510 removes
this type from wast output, so this test needed to be updated first to
keep the rollers happy.
@tlively tlively requested a review from kripken December 11, 2019 23:06
@tlively tlively changed the title Generalize test in prep for #binaryen/2510 Generalize test in prep for WebAssembly/binaryen#2510 Dec 11, 2019
@tlively tlively changed the title Generalize test in prep for WebAssembly/binaryen#2510 Generalize test in prep for binaryen#2510 Dec 11, 2019
@kripken kripken merged commit ba26d98 into emscripten-core:incoming Dec 12, 2019
belraquib pushed a commit to belraquib/emscripten that referenced this pull request Dec 23, 2020
…-core#10011)

This test unnecessarily checked for the presence of an explicit type
in a function definition in a .wast. The upcoming PR emscripten-core#2510 removes
this type from wast output, so this test needed to be updated first to
keep the rollers happy.
@tlively tlively deleted the generalize-test branch February 5, 2024 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants