You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following tests fail to report the intended errors (most often it is missing the intended number of errors; sometimes failing to report any error at all), not because of a bug in the compiler, but rather because the test was written in a manner that assumes lexical lifetimes.
This issue is just documenting these cases (and I will try to add to the list if more are discovered); a follow-up PR will have the necessary updates to the tests.
(Some of the cases currently listed are only currently slated as "needs investigation", either to whether it should be strengthened, or what the original intent of the test even was, etc. As those questions are resolved, they will be either have their checkbox marked, or just crossed off entirely.)
huh; I changed my mind. Found way to strengthen test I'm happy with. Should double-check original intent of test vs ifetime-errors/ex3-both-anon-regions.rs though.
lifetimes/borrowck-let-suggestion.rs
span/borrowck-let-suggestion-suffixes.rs
span/issue-36537.rs
span/mut-ptr-cant-outlive-ref.rs
span/range-2.rs
span/regionck-unboxed-closure-lifetimes.rs
span/send-is-not-static-std-sync.rs
span/slice-borrow.rs
span/vec_refs_data_with_early_death.rs
(This list of tests is drawn from an informal paper document that I have been using to keep notes for myself as I work on this...)
The text was updated successfully, but these errors were encountered:
…robust-wrt-nll, r=nikomatsakis
make ui tests robust with respect to NLL
This PR revises the `ui` tests that I could quickly identify that:
1. previously had successful compilations under non-lexical lifetimes (NLL) because they assumed lexical lifetimes, but
2. such assumption of lexical lifetimes was actually not necessarily part of the spirit of the original issue/bug we want to witness.
In many cases, this is simply a matter of adding a use of a borrow so that it gets extended long enough to observe a conflict.
(In some cases the revision was more subtle, such as adding a destructor, or revising the order of declaration of some variables.)
----
With these test revisions in place, I subsequently updated the expected stderr output under the NLL compiletest mode. So now we should get even more testing of NLL than we were before.
Fixrust-lang#51025
pnkfelix
changed the title
several ui tests need to be strenghtened to properly test NLL mode
several ui tests need to be strengthened to properly test NLL mode
Aug 15, 2018
The following tests fail to report the intended errors (most often it is missing the intended number of errors; sometimes failing to report any error at all), not because of a bug in the compiler, but rather because the test was written in a manner that assumes lexical lifetimes.
This issue is just documenting these cases (and I will try to add to the list if more are discovered); a follow-up PR will have the necessary updates to the tests.
(Some of the cases currently listed are only currently slated as "needs investigation", either to whether it should be strengthened, or what the original intent of the test even was, etc. As those questions are resolved, they will be either have their checkbox marked, or just crossed off entirely.)
codemap_tests/one_line.rscodemap_tests/overlapping_spans.rslet (a, b);
#51036let (a, b);
#51036let (a, b);
#51036issue-17263.rsBox
, which was intended.(This list of tests is drawn from an informal paper document that I have been using to keep notes for myself as I work on this...)
The text was updated successfully, but these errors were encountered: