-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Octal literals #6563
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Proposed syntax: |
An |
Meh, closing, not important. |
Please reconsider this feature request; Unix permissions are most easily expressed using octal permissions. While expressing permissions via binary 0b111_101_101 is workable, I suspect most of us would do the mental arithmetic to re-write that to 0o755. Clever macros can mask some of this -- see e.g., https://gist.github.com/kmcallister/7312179 -- but asking each chmod() or umask() user to either re-implement them or discover and import such a package feels awkward compared to supporting 0o ... syntax directly in the language. Thanks |
@setharnold see #10243 |
Associated with Issue #6563. Useful for Apollo Guidance Computer simulation, Unix file system permissions, and maybe one or two other things.
Since fixed. |
Re-write shadow lints changelog: Move shadow_unrelated to restriction changelog: The shadow lints find a lot more shadows and are not limited to certain patterns Drastically simplifies the implementation. Catches a lot more cases. I removed the "initialization happens here" note. It is not helpful IMO. Closes rust-lang#318 Fixes rust-lang#2890 Fixes rust-lang#6563 Fixes rust-lang#7588 Fixes rust-lang#7620
It's a strange omission. There are hex and binary literals, but no octal!
The text was updated successfully, but these errors were encountered: