| Age | Commit message (Collapse) | Author | Lines |
|
|
|
|
|
a default impl should never be considered as implementing the
trait on its own -- regardless of whether it contains all items
or not
|
|
a `default impl` need not include all items from the trait
a `default impl` alone does not mean that a type implements the trait
|
|
Helps to avoid hitting path limits on Windows
|
|
Paths to object files generated from them were too long and caused errors
|
|
|
|
`[default] [unsafe] impl` and typecheck
|
|
pr review
|
|
this commit implements the first step of the `default impl` feature:
all items in a `default impl` are (implicitly) `default` and hence
specializable.
In order to test this feature I've copied all the tests provided for the
`default` method implementation (in run-pass/specialization and
compile-fail/specialization directories) and moved the `default` keyword
from the item to the impl.
See referenced issue for further info
|
|
Projections can generate lifetime variables with equality constraints,
that will not be resolved by `resolve_type_vars_if_possible`, so substs
need to be lifetime-erased after that.
Fixes #36848.
|
|
For legacy reasons (presumably), Windows does not permit files name aux.
|
|
Instead of finding aux-build files in `auxiliary`, we now search for an
`aux` directory relative to the test. So if your test is
`compile-fail/foo.rs`, we would look in `compile-fail/aux`. Similarly,
we ignore the `aux` directory when searching for tets.
|
|
|
|
|
|
|
|
|