You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
* Fix kani-compiler logs + add json option
This change fixesrust-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
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.
The text was updated successfully, but these errors were encountered: