Skip to content

Boolean literals are not Number literals #19985

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

Closed
wants to merge 1 commit into from
Closed

Boolean literals are not Number literals #19985

wants to merge 1 commit into from

Conversation

th0114nd
Copy link
Contributor

No description provided.

@th0114nd
Copy link
Contributor Author

The current indentation level would indicate that Boolean literals are on the same level as Integer and Float literals under Number literals, unindenting moves it to the same scope as Character and string literals, Byte and byte string literals, and Number literals under Literals.

@alexcrichton
Copy link
Member

Sadly our automation doesn't deal well with the source repository being deleted, could you re-fork and remake this PR? Sorry for the inconvenience!

@th0114nd
Copy link
Contributor Author

Remade here: #19996

lnicola pushed a commit to lnicola/rust that referenced this pull request Jun 16, 2025
…v-ast-id

fix: Support spans with proc macro servers from before the ast id changes
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