Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compile speed #8802

Closed
wants to merge 13 commits into from
Closed

Compile speed #8802

wants to merge 13 commits into from

Conversation

pcwalton
Copy link
Contributor

r? @brson

They are still present as part of the borrow check.
For example, `foo::<T>::bar::<U>`.

This doesn't enforce that the type parameters are in the right
positions, however.
…aths.

This removes the stacking of type parameters that occurs when invoking
trait methods, and fixes all places in the standard library that were
relying on it. It is somewhat awkward in places; I think we'll probably
want something like the `Foo::<for T>::new()` syntax.
10% win or so for small crates.
This does not implement lazy symbol resolution yet.
This is only for implementations defined in the same crate as the trait they
implement.
bors added a commit that referenced this pull request Aug 28, 2013
@bors bors closed this Aug 28, 2013
xFrednet pushed a commit to xFrednet/rust that referenced this pull request May 21, 2022
… r=llogiq

Optionally allow `expect` and `unwrap` in tests

This addresses rust-lang#1015, except it makes the new behavior optional.

The reason for the msrv-related changes is as follows.

Rather than expand `check_methods` list of arguments, it seemed easier to make `check_methods` a method of `Methods`, so that `check_methods` could access `Methods`' fields.

`check_methods` had an `msrv` parameter, which I consequently made a field of `Methods`. But, to avoid adding a lifetime parameter to `Methods`, I made the field type `Option<RustcVersion>` instead of the parameter's existing type, `Option<&RustcVersion>`. This seemed sensible since `RustcVersion` implements `Copy`. But this broke a lot of code that expected an `Option<&RustcVersion>` or `&Option<RustcVersion>`. I changed all of those occurrences to `Option<RustcVersion>`. IMHO, the code is better as a result of these changes, though.

The msrv-related changes are in their own commit to (hopefully) ease review.

Closes rust-lang#1015

changelog: optionally allow `expect` and `unwrap` in tests

r? `@llogiq`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants