Skip to content

Upvars in lambdas can be written to, with silly results #805

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
msullivan opened this issue Aug 5, 2011 · 0 comments
Closed

Upvars in lambdas can be written to, with silly results #805

msullivan opened this issue Aug 5, 2011 · 0 comments
Labels
A-type-system Area: Type system

Comments

@msullivan
Copy link
Contributor

Right now, if you write to an upvar in a copying closure, the value in the closure will be changed. This means that subsequent invocations of the function will see that value but the enclosing scope will not. This kind of sucks.

We should disallow writes to variables closed over by copying.

@ghost ghost assigned msullivan Aug 5, 2011
@msullivan msullivan removed their assignment Jun 16, 2014
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
ZuseZ4 added a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
celinval added a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
* Fix kani-compiler logs + add json option

This change fixes rust-lang#785. It allow users to configure the Kani logs via
KANI_LOG environment variable as well as via --log-level argument. Note
that the former allows finer grain control on a per crate configuration.

We also support the RUSTC_LOG variable to control the underlying rustc
packages. In order to control the rustc logging, we would need to match
the exact version of the tracing crate used by rustc. To avoid that,
we're keeping them separate.

* Use new --log-level option instead of env variable
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-type-system Area: Type system
Projects
None yet
Development

No branches or pull requests

1 participant