Use a consistent metavariable for types in the tutorial #2461
Labels
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Comments
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Sep 22, 2022
add special exception for std_miri_test crate to call std-only functions These being the unit tests of std, they have their own copy of `std::sys` and `std::thread`, so the existing check says this is not std. The check is correct but we want to allow this so we just hard-code the crate name. The point of this `frame_in_std` check is to prevent people from directly interacting with shims that aren't really properly implemented, but it doesn't need to be 100% airtight. If someone really wants to call their crate `std_miri_test` in order to access some broken shims... they can keep the pieces.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The tutorial sometimes uses
T(section 3.5) and sometimes usesTYPE(section 6) as a metavariable for types. Consolidate these (I think we should stick withT).The text was updated successfully, but these errors were encountered: