-
Notifications
You must be signed in to change notification settings - Fork 16
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
Tracking issue for not crashing on the rustc test suite #145
Comments
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
1 similar comment
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
Summary of the results: |
I might have been too lenient in my recent PRs: I think we're now treating rust errors as panics. See also #306. |
Summary of the results: |
Summary of the results: |
In #136 we added a script that runs charon on the rustc test suite and displays the results. As we'd like to support a large portion of the rust language, we track in this issue our results on these tests.
Our first aim is to never panic. Initial results:
(Please don't post on this conversation, it's mean for automated posting)
The text was updated successfully, but these errors were encountered: