-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
[RFC 2011] Basic compiler infrastructure #97450
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for splitting this up. As a next smaller step, maybe just add binary operations and nothing else?
src/test/ui/rfc-2011-nicer-assert-messages/feature-gate-generic_assert.rs
Show resolved
Hide resolved
Done. Thank you for the review Sure! Next step binary operations will be. |
@bors r+ |
📌 Commit aa115eb has been approved by |
@bors rollup |
Rollup of 5 pull requests Successful merges: - rust-lang#97420 (Be a little nicer with casts when formatting `fn` pointers) - rust-lang#97450 ([RFC 2011] Basic compiler infrastructure) - rust-lang#97599 (Fix JSON reexport ICE) - rust-lang#97617 (Rustdoc anonymous reexports) - rust-lang#97636 (Revert rust-lang#96682.) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Splitting #96496 into smaller pieces as was done in #97233. Hope review will be easier.
This PR practically contains no logic and only serves as a building ground for the actual code that will be placed in a posterior step.
context.rs
to place the newassert!
logic. Has a lot of unused elements but all of them are used by the implementation.sym
identifiers that are mostly based on the library elements -> https://github.com/rust-lang/rust/blob/master/library/core/src/asserting.rsassert.rs
to branch tocontext.rs
if the unstable flag is enabled.