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

Number literal defaulting is incorrectly worded #29

Closed
steveklabnik opened this issue Mar 29, 2017 · 1 comment
Closed

Number literal defaulting is incorrectly worded #29

steveklabnik opened this issue Mar 29, 2017 · 1 comment
Labels
C-bug Incorrect statements, terminology, or rendering issues

Comments

@steveklabnik
Copy link
Member

https://doc.rust-lang.org/nightly/reference/tokens.html#integer-literals says

If the program context under-constrains the type, it defaults to the signed 32-bit integer

and https://doc.rust-lang.org/nightly/reference/tokens.html#floating-point-literals says

If the program context under-constrains the type, it defaults to f64

I don't believe this is true, it's if there are no constraints, not under-constraints.

This is one to get lang team sign-off for.

@steveklabnik steveklabnik added the C-bug Incorrect statements, terminology, or rendering issues label Mar 29, 2017
@jaystrictor
Copy link

This issue was opened based on a discussion on users.rust-lang.org.

However, as it turned out, the problem does not occur for trait method calls, so this should rather be a bug in the rust compiler. I opened a corresponding bug report there.

So I think this can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Incorrect statements, terminology, or rendering issues
Projects
None yet
Development

No branches or pull requests

2 participants