Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Language FAQ is out of date #3386

Closed
catamorphism opened this issue Sep 4, 2012 · 1 comment
Closed

Language FAQ is out of date #3386

catamorphism opened this issue Sep 4, 2012 · 1 comment
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Milestone
old 1.0 milestone

Comments

@catamorphism
Copy link
Contributor

https://github.com/mozilla/rust/wiki/Doc-language-FAQ

The code example is clearly out of date. Didn't look if the rest of the FAQ needs updating too.
@catamorphism
Copy link
Contributor Author

I updated the code example and the obviously out-of-date things in the questions and answers. I didn't try compiling the code example, so I probably made a mistake. For now, though, I'm happier with the FAQ.

@metajack metajack mentioned this issue Apr 25, 2013
Closed
RalfJung pushed a commit to RalfJung/rust that referenced this issue Mar 23, 2024
@bors
Auto merge of rust-lang#3386 - RalfJung:ci, r=RalfJung
dd5b4f5 
fix Zulip topic for PR-creation message
jaisnan pushed a commit to jaisnan/rust-dev that referenced this issue Jul 29, 2024
@celinval
Add two new CI workflows to check Kani against verify-rust-std (rus…
70bd021 
…t-lang#3386)

This PR adds the following workflows:
1. `verify-std-check`: This workflow will run either in a PR or via
workflow call. It pulls the `main` branch of `verify-rust-std`
repository, and see if it can verify the repo with the new Kani version
from HEAD.
   - If verification succeeds, the workflow will succeed.
   - If the verification fails and this is a PR, the workflow will compare
the verification result against the base of the PR. The workflow will
succeed if the results match*.
2. `verify-std-update`: This workflow will run the `verify-std-check`
workflow. If it succeeds, it will update the `verify-rust-std` branch
from HEAD. This workflow will fail if `features/verify-rust-std` branch
diverges, and a merge is required.

The motivation for this PR is to help us identify any changes to Kani
that may break the Rust verification repository, and to keep the
`verify-rust-std` up to date as much as possible.

* The fallback logic is needed since toolchain upgrades can potentially
break the std verification. This will happen in cases where the new
toolchain version is incompatible with the library version from the
`verify-rust-std`. Those cases should not interfere with Kani
development, and they should be fixed when we update the
`verify-rust-std` repo.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
old 1.0 milestone
Development

No branches or pull requests
1 participant
@catamorphism