-
Notifications
You must be signed in to change notification settings - Fork 349
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
Rustup for retagging #506
Rustup for retagging #506
Conversation
…n with optimizations and we can finally stop mutating the state on deref
Not all of them pass validation...
The retagging PR is in nightly now. |
Yay Travis is green :) |
size: Size, | ||
) -> EvalResult<'tcx> { | ||
// This is like mutating | ||
self.use_and_maybe_re_borrow(ptr, size, UsageKind::Write, None) |
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.
there's nothing else happening? is the fact that the allocation is gone enough?
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.
I think so. What else should happen?
There's a FIXME for doing something with barriers later.
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.
yea... I was thinking like "clearing the borrow stack", but that's kind of of useless on a deallocated allocation... I can't think of anything here. I was mostly surprised how easy this case seems
Matches rust-lang/rust#55316
Also make our use of
-Z
flags more consistent.