-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Change how fn(&T)
parses
#3535
Comments
an explicit variable name. (Step one to changing the defaults) First step to #3535
I did the patch to disable modes with unamed arguments. However, we have now a quite confusing error message:
So I modify the argument dump to display:
I wonder if this display could become a new syntax to specify modes for unamed arguments (that is adding a colon between mode and type). |
Oh, good point (regarding the conversion of the type to a string). However, I don't think a new syntax is needed, because modes will be removed shortly. |
…ping funcion prototype
I take it this can be closed, since Vincent's patch is in incoming. |
Try to solve issue 3417.
update host-float comments Turns out most of these do not have guaranteed precision anyway so it's fine to use host floats (see rust-lang#121793 and rust-lang#118217). The exception are sqrt and mul_add, tracked at rust-lang/miri#3534 and rust-lang/miri#2995.
Right now,
fn(&T)
parses asfn(&v: T)
rather thanfn(v: &T)
. This should be changed so that modes require explicit variable names. We would also of course then need to update the various legacyfn()
types that appear in rustc and elsewhere.The text was updated successfully, but these errors were encountered: