Skip to content

Reformat under the major agreed syntax changes #563

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
graydon opened this issue Jun 23, 2011 · 4 comments
Closed

Reformat under the major agreed syntax changes #563

graydon opened this issue Jun 23, 2011 · 4 comments
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) A-pretty Area: Pretty printing (including `-Z unpretty`) C-cleanup Category: PRs that clean code up or issues documenting cleanup.

Comments

@graydon
Copy link
Contributor

graydon commented Jun 23, 2011

There's a bunch of syntax changes pending. Teach pp and parser to do it, then snapshot, reformat, and resnap.

@ghost ghost assigned graydon Jun 23, 2011
@marijnh
Copy link
Contributor

marijnh commented Aug 18, 2011

This is done (a few points from the syntax reform e-mail remain open, these are pattern extensions -- I'm opening separate bugs for them).

@marijnh marijnh closed this as completed Aug 18, 2011
@graydon graydon reopened this Aug 18, 2011
@graydon
Copy link
Contributor Author

graydon commented Aug 18, 2011

Not quite! While not mentioned in the syntax reform email, .() still needs to change to [] now that [] is freed up.

@marijnh
Copy link
Contributor

marijnh commented Aug 18, 2011

good point. i'll handle that tomorrow

@pcwalton
Copy link
Contributor

.() is now [] as of a7d837b, so perhaps we can close this now?

@graydon graydon removed their assignment Jun 16, 2014
arielb1 pushed a commit to arielb1/rust that referenced this issue Apr 10, 2015
add in unresolved questions from the RFC discussion.
celinval added a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
* Add --enable-unstable option

Unstable options now require users to explicitly enable them. This is
important because the unstable options can be unsound or give spurious
CEX.

* Disable spurious pointer checks by default

We have been seeing a lot of spurious CEX related to pointer out of
bounds checks in arithmetic operations. It is actually valid rust in
some cases, and we can't differentiate the valid ones from the invalid
ones today. Thus, I'm disabling them by default.

Note that dereferencing invalid pointers is caught by different checks
and they should not be affected by this change.

This changes fixes rust-lang#563 and rust-lang#763.

Co-authored-by: Zyad Hassan <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) A-pretty Area: Pretty printing (including `-Z unpretty`) C-cleanup Category: PRs that clean code up or issues documenting cleanup.
Projects
None yet
Development

No branches or pull requests

3 participants