bootstrap compiler ignores unknown names #154
Comments
|
Closed by 74cb950. |
oli-obk
pushed a commit
to oli-obk/rust
that referenced
this issue
Jul 19, 2017
partially update for latest rustc nightly
keeperofdakeys
pushed a commit
to keeperofdakeys/rust
that referenced
this issue
Dec 12, 2017
Add IP v6 group membership options to OpenBSD build
kazcw
pushed a commit
to kazcw/rust
that referenced
this issue
Oct 23, 2018
Aaron1011
pushed a commit
to Aaron1011/rust
that referenced
this issue
Oct 26, 2020
…ft-606eee5 Bump cranelift from `fe081d3` to `606eee5`
bors
pushed a commit
to rust-lang-ci/rust
that referenced
this issue
Oct 1, 2021
…nt-type Change vectors to be generic over element type.
antoyo
added a commit
to antoyo/rust
that referenced
this issue
Jun 7, 2022
Fix error related to var tracking assignments
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Apr 10, 2024
Clean up tests/ui by removing `does-nothing.rs` In [a previous PR](rust-lang#123297 (comment)), it was suggested that this test be removed: > it's testing a basic diagnostic for an unknown variable (added over a decade ago for rust-lang#154) that is already covered by probably dozens or hundreds of other tests. It was then suggested that [opening a new PR](rust-lang#123563 (comment)) for this would be more organized. I'm setting this as a draft, as: 1. The tests/ui directory is rather disorganized, a large quantity of tests are not even contained inside their own directories. This PR could turn into "clean up the UI tests directory", if I were to place everything into categories (for example, everything related to CLI flags could get placed in a cli directory). 2. This will have a merge conflict with rust-lang#123563 should that get merged. I trust that _this time_, I won't run into [The Incident](rust-lang#123297 (comment)) while rebasing. Edit: Yay, I did it properly!
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Apr 10, 2024
Rollup merge of rust-lang#123568 - Oneirical:delete-tests, r=wesleywiser Clean up tests/ui by removing `does-nothing.rs` In [a previous PR](rust-lang#123297 (comment)), it was suggested that this test be removed: > it's testing a basic diagnostic for an unknown variable (added over a decade ago for rust-lang#154) that is already covered by probably dozens or hundreds of other tests. It was then suggested that [opening a new PR](rust-lang#123563 (comment)) for this would be more organized. I'm setting this as a draft, as: 1. The tests/ui directory is rather disorganized, a large quantity of tests are not even contained inside their own directories. This PR could turn into "clean up the UI tests directory", if I were to place everything into categories (for example, everything related to CLI flags could get placed in a cli directory). 2. This will have a merge conflict with rust-lang#123563 should that get merged. I trust that _this time_, I won't run into [The Incident](rust-lang#123297 (comment)) while rebasing. Edit: Yay, I did it properly!
celinval
pushed a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
* Improve some regression tests and add some more. * Add more assertions to a test. * Revert changes to trait regressions. * Add comments explaining dereferencing raw address test.
celinval
pushed a commit
to celinval/rust-dev
that referenced
this issue
Nov 29, 2024
Towards rust-lang#76 ### Changes * Adds contracts for `<*const T>::offset_from`. * Adds harnesses for the function verifying: * All integer types * Tuples (composite types) * Unit Type * Accomplishes this using a macro. By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses. --------- Co-authored-by: Carolyn Zech <cmzech@amazon.com>
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
// BEGIN CODE
// -- rust --
fn main() {
log "doing";
this_does_nothing_what_the;
log "boing";
}
// END CODE
The following code compiles, wouldn't it be wiser to have the compiler report an error about "this_does_nothing_what_the"?
The text was updated successfully, but these errors were encountered: