Skip to content

#7081: Further syntax::visit refactors #9453

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

Merged
merged 2 commits into from
Sep 24, 2013

Conversation

pnkfelix
Copy link
Member

r? anyone.

Part of #7081.

More refactorings of the syntax::visit::Visitor implementations, folding so-called "environments" into the visitor impl when the latter was previously a trivial unit struct.

As usual, this refactoring only applies when the environments are not actually carrying state that is meant to be pushed and popped as we traverse the expression. (For an example where the environment isn't just passed through, see the visit_fn in liveness.rs.)

Got rid of a bit of @-allocation in borrowck.

Both cases should be pure-refactorings.

bors added a commit that referenced this pull request Sep 24, 2013
…s, r=alexcrichton

r? anyone.

Part of #7081.

More refactorings of the syntax::visit::Visitor implementations, folding so-called "environments" into the visitor impl when the latter was previously a trivial unit struct.

As usual, this refactoring only applies when the environments are not actually carrying state that is meant to be pushed and popped as we traverse the expression.  (For an example where the environment *isn't* just passed through, see the `visit_fn` in `liveness.rs`.)

Got rid of a bit of @-allocation in borrowck.

Both cases should be pure-refactorings.
@bors bors closed this Sep 24, 2013
@bors bors merged commit 4f691cd into rust-lang:master Sep 24, 2013
djkoloski pushed a commit to djkoloski/rust that referenced this pull request Sep 21, 2022
[`assertions_on_result_states`]: Fix suggestion when `assert!` is not in a statement.

fix rust-lang/rust-clippy#9450

changelog: [`assertions_on_result_states`]: Fix suggestion when `assert!` is not in a statement.
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.

3 participants