rust/src/test/ui/array-slice-vec, branch 1.59.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.59.02021-12-09T22:03:52+00:00Add needs-unwind to tests that depend on panicking2021-12-09T22:03:52+00:00David Koloskidjkoloski@gmail.com2021-12-03T15:32:51+00:00urn:sha1:ea68758299a89556e67f0bfffffb19c0c8346e8a
This directive isn't automatically set by compiletest or x.py, but can
be turned on manually for targets that require it.
Move some tests to more reasonable directories2021-11-18T15:09:34+00:00Caioc410.f3r@gmail.com2021-11-18T15:09:34+00:00urn:sha1:41d9abd76cd514aca23e3409fe6896a3a7d61d1aMove some tests to more reasonable directories2021-11-06T18:35:20+00:00Caioc410.f3r@gmail.com2021-11-06T18:35:20+00:00urn:sha1:7fd15f09008dd72f40d76a5bebb60e3991095a5fAuto merge of #89110 - Aaron1011:adjustment-span, r=estebank2021-09-30T01:40:30+00:00borsbors@rust-lang.org2021-09-30T01:40:30+00:00urn:sha1:4aa7879b559ccf7f82bcce2a8e532ea307697ea9
Use larger span for adjustment THIR expressions
Currently, we use a relatively 'small' span for THIR
expressions generated by an 'adjustment' (e.g. an autoderef,
autoborrow, unsizing). As a result, if a borrow generated
by an adustment ends up causing a borrowcheck error, for example:
```rust
let mut my_var = String::new();
let my_ref = &my_var
my_var.push('a');
my_ref;
```
then the span for the mutable borrow may end up referring
to only the base expression (e.g. `my_var`), rather than
the method call which triggered the mutable borrow
(e.g. `my_var.push('a')`)
Due to a quirk of the MIR borrowck implementation,
this doesn't always get exposed in migration mode,
but it does in many cases.
This commit makes THIR building consistently use 'larger'
spans for adjustment expressions. These spans are recoded
when we first create the adjustment during typecheck. For
example, an autoref adjustment triggered by a method call
will record the span of the entire method call.
The intent of this change it make it clearer to users
when it's the specific way in which a variable is
used (for example, in a method call) that produdes
a borrowcheck error. For example, an error message
claiming that a 'mutable borrow occurs here' might
be confusing if it just points at a usage of a variable
(e.g. `my_var`), when no `&mut` is in sight. Pointing
at the entire expression should help to emphasize
that the method call itself is responsible for
the mutable borrow.
In several cases, this makes the `#![feature(nll)]` diagnostic
output match up exactly with the default (migration mode) output.
As a result, several `.nll.stderr` files end up getting removed
entirely.
Remove box syntax from most places in src/test outside of the issues dir2021-09-26T02:07:44+00:00est31MTest31@outlook.com2021-08-25T00:39:40+00:00urn:sha1:6550021124451628b1efc60c59284465b109e3aaUse larger span for adjustments on method calls2021-09-25T15:00:41+00:00Aaron Hillaa1ronham@gmail.com2021-09-16T20:01:22+00:00urn:sha1:4d66986e090abed11c1aae9602f23385f94154fa
Currently, we use a relatively 'small' span for THIR
expressions generated by an 'adjustment' (e.g. an autoderef,
autoborrow, unsizing). As a result, if a borrow generated
by an adustment ends up causing a borrowcheck error, for example:
```rust
let mut my_var = String::new();
let my_ref = &my_var
my_var.push('a');
my_ref;
```
then the span for the mutable borrow may end up referring
to only the base expression (e.g. `my_var`), rather than
the method call which triggered the mutable borrow
(e.g. `my_var.push('a')`)
Due to a quirk of the MIR borrowck implementation,
this doesn't always get exposed in migration mode,
but it does in many cases.
This commit makes THIR building consistently use 'larger'
spans for adjustment expressions
The intent of this change it make it clearer to users
when it's the specific way in which a variable is
used (for example, in a method call) that produdes
a borrowcheck error. For example, an error message
claiming that a 'mutable borrow occurs here' might
be confusing if it just points at a usage of a variable
(e.g. `my_var`), when no `&mut` is in sight. Pointing
at the entire expression should help to emphasize
that the method call itself is responsible for
the mutable borrow.
In several cases, this makes the `#![feature(nll)]` diagnostic
output match up exactly with the default (migration mode) output.
As a result, several `.nll.stderr` files end up getting removed
entirely.
Ignore automatically derived impls of `Clone` and `Debug` in dead code analysis2021-09-09T17:49:07+00:00Fabian Wolfffabian.wolff@alumni.ethz.ch2021-05-21T17:35:49+00:00urn:sha1:79adda930f9b607ecb4819ed7abcf1cd285e938a`feature(const_generics)` -> `feature(const_param_types)`2021-08-30T09:00:21+00:00lcnrrust@lcnr.de2021-08-27T16:04:57+00:00urn:sha1:0c28e028b6f45f33447f24de7dd762b8599b7a4eLint for unused borrows as part of UNUSED_MUST_USE2021-06-18T07:09:40+00:00hi-rustinrustin.liu@gmail.com2021-06-18T07:09:40+00:00urn:sha1:88abd7d81d585ba31cab1ca404a5ed6b44511f98remove const_fn feature gate from const tests2021-04-29T07:27:45+00:00Ralf Jungpost@ralfj.de2021-04-26T12:53:41+00:00urn:sha1:3752c6bb40e9e05bbc10d286c508742242448fa3