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

Explain in literal expression how it translate the token to the value #939

Open
Havvy opened this issue Jan 21, 2021 · 2 comments
Open

Explain in literal expression how it translate the token to the value #939

Havvy opened this issue Jan 21, 2021 · 2 comments
Labels
A-expressions Area: Expressions Language Cleanup Improvements to existing language which is correct but not clear, or missing examples, or the like. New Content Missing features or aspects of language not currently documented.

Comments

@Havvy
Copy link
Contributor

Havvy commented Jan 21, 2021

Right now the literal tokens chapter describes the behavior of literal expressions and not just the tokens. The behavior of matching the token to a specific primitive value should be described in the literal expressions chapter while the token literals chapter just describes the tokens.

@Havvy Havvy added Language Cleanup Improvements to existing language which is correct but not clear, or missing examples, or the like. A-expressions Area: Expressions labels Jan 21, 2021
@ehuss
Copy link
Contributor

ehuss commented Jan 21, 2021

Can you clarify exactly which parts you are referring to? One oddity I see is the discussion about type inference with unsuffixed numbers, but I'm curious what else you're thinking of.

@Havvy Havvy changed the title Split out literal expression and literal tokens Explain in literal expression how it translate the token to the value Jan 22, 2021
@Havvy Havvy added the New Content Missing features or aspects of language not currently documented. label Jan 22, 2021
@Havvy
Copy link
Contributor Author

Havvy commented Jan 22, 2021

Ah, that's what I get for not actually checking the tokens page (it's a long page...) while quickly looking at how sparse https://doc.rust-lang.org/reference/expressions/literal-expr.html is. This is actually something just not documented, though yeah, that section on type inference should be moved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-expressions Area: Expressions Language Cleanup Improvements to existing language which is correct but not clear, or missing examples, or the like. New Content Missing features or aspects of language not currently documented.
Projects
None yet
Development

No branches or pull requests

2 participants