-
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
Treatment of bound / free regions is wrong #2981
Comments
Another test case:
|
nikomatsakis
added a commit
that referenced
this issue
Jul 25, 2012
nikomatsakis
added a commit
that referenced
this issue
Jul 25, 2012
ghost
assigned nikomatsakis
Jul 26, 2012
This is fixed, although I'd still to convert the codebase to using debruijn indices or something similar. |
RalfJung
pushed a commit
to RalfJung/rust
that referenced
this issue
Jul 23, 2023
style checks: use latest rustc for cron job
celinval
pushed a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
The values of environment variables in the benchcomp configuration file can now contain strings of the form '${var}'. Benchcomp will replace these strings with the value of the environment variable 'var'. This is intended to allow users to have several benchcomp variants, each of which differs only in the environment. This fixes rust-lang#2981.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current code for handling bound regions is not right. We need to track node-ids uniformly and not only for free regions. Here is an example of a test case that fails. I have a partial fix for this, but not yet committed.
The text was updated successfully, but these errors were encountered: