Skip to content
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

Add migration code for f32/f64. #1364

Merged

Conversation

sunfishcode
Copy link
Member

Add a WIT_REQUIRE_F32_F64 environment variable controlling whether the float32 and float64 syntax is acccepted, similar to the transition for semicolons.

Add a `WIT_REQUIRE_F32_F64` environment variable controlling whether
the `float32` and `float64` syntax is acccepted, similar to the
transition for semicolons.
Copy link
Member

@alexcrichton alexcrichton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@alexcrichton alexcrichton merged commit eced912 into bytecodealliance:main Jan 9, 2024
15 checks passed
sunfishcode added a commit to sunfishcode/wasm-tools that referenced this pull request Mar 21, 2024
Following up on bytecodealliance#1364 which added `f32` and `f64` parsing support,
this PR renames the types `float32` and `float64` to `f32` and `f64`.

The old names are still accepted for now.

WebAssembly/component-model#277
sunfishcode added a commit to sunfishcode/wasm-tools that referenced this pull request Mar 21, 2024
As discussed [here], and following up on bytecodealliance#1364 which added `f32`
and `f64` parsing support, this PR renames the types `float32`
and `float64` to `f32` and `f64`.

The old names are still accepted by the parser for compatibility.

[here]: WebAssembly/component-model#277
sunfishcode added a commit to sunfishcode/wasm-tools that referenced this pull request Mar 21, 2024
As discussed [here], and following up on bytecodealliance#1364 which added `f32`
and `f64` parsing support, this PR renames the types `float32`
and `float64` to `f32` and `f64`.

The old names are still accepted by the parser for compatibility.

[here]: WebAssembly/component-model#277
github-merge-queue bot pushed a commit that referenced this pull request Mar 21, 2024
As discussed [here], and following up on #1364 which added `f32`
and `f64` parsing support, this PR renames the types `float32`
and `float64` to `f32` and `f64`.

The old names are still accepted by the parser for compatibility.

[here]: WebAssembly/component-model#277
alexcrichton added a commit to alexcrichton/wasm-tools that referenced this pull request Sep 11, 2024
This commit continues the transition started in bytecodealliance#1364 to rename the
`float32 `and `float64` types in WIT to `f32` and `f64`. Now that
support has been present for some time to parse `f32` and `f64` this
commit flips the WIT parser to requiring it by default. The error
message for `float32` and `float64` has additionally been updated to
explain a bit more about this transition.
alexcrichton added a commit to alexcrichton/wasm-tools that referenced this pull request Sep 12, 2024
This commit continues the transition started in bytecodealliance#1364 to rename the
`float32 `and `float64` types in WIT to `f32` and `f64`. Now that
support has been present for some time to parse `f32` and `f64` this
commit flips the WIT parser to requiring it by default. The error
message for `float32` and `float64` has additionally been updated to
explain a bit more about this transition.
github-merge-queue bot pushed a commit that referenced this pull request Sep 12, 2024
This commit continues the transition started in #1364 to rename the
`float32 `and `float64` types in WIT to `f32` and `f64`. Now that
support has been present for some time to parse `f32` and `f64` this
commit flips the WIT parser to requiring it by default. The error
message for `float32` and `float64` has additionally been updated to
explain a bit more about this transition.
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.

2 participants