-
Notifications
You must be signed in to change notification settings - Fork 83
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
Rename float32
/float64
to f32
/f64
.
#324
Rename float32
/float64
to f32
/f64
.
#324
Conversation
The `float32` and `float64` types are being [renamed to `f32` and `f64`]. All the main tools have been updated to accept both old and new names for now, so there's no urgency to change anything, but users who wish to can now start switching to the new `f32`/`f64` names. [renamed to `f32` and `f64`]: WebAssembly#277
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this! Could you also s/Float32/F32/ and s/Float64/F64/ in CanonicalABI.md and canonical-abi/definitions.py?
In terms of merging into this repo: if the tools are already updated to accept f32
/f64
, then it seems like we can merge (after a day or two for final comments); is that right?
|
(Oops, I forgot to merge this earlier.) |
The component-model type "float32" was [renamed to "f32"], so rename Wave's type to match. [renamed to "f32"]: WebAssembly/component-model#324
The component-model type "float32" was [renamed to "f32"], so rename Wave's type to match. [renamed to "f32"]: WebAssembly/component-model#324
The
float32
andfloat64
types are beingrenamed to
f32
andf64
. All the main tools have been updated to accept both old and new names for now, so there's no urgency to change anything, but users who wish to can now start switching to the newf32
/f64
names.