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

Add doc comment for extra::url::query_to_str #10532

Merged
merged 1 commit into from
Nov 18, 2013
Merged

Add doc comment for extra::url::query_to_str #10532

merged 1 commit into from
Nov 18, 2013

Conversation

dhodder
Copy link
Contributor

@dhodder dhodder commented Nov 17, 2013

Hello. This is just a tiny doc update -- I'm new here, so apologies if I'm doing it wrong.

bors added a commit that referenced this pull request Nov 17, 2013
Hello.  This is just a tiny doc update -- I'm new here, so apologies if I'm doing it wrong.
@bors bors closed this Nov 18, 2013
@bors bors merged commit 48f76a0 into rust-lang:master Nov 18, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Mar 24, 2023
Significantly optimize `significant_drop_tightening`

The lint is very slow as it doesn't cache the deeply nested check for the attribute. If we cache it, we can reduce the time spent on checking `rustc_borrowck` from 28s to 9s, which is a nice improvement. In the profile, the time inside `has_sig_drop_attr` goes from 66% to 0.2%, which is a lot more reasonable.

<details>
<summary>Flame graphs</summary>

Before (all the tall `clippy` towers are `has_sig_drop_attr`):
![before](https://user-images.githubusercontent.com/48135649/227037243-bcd93bbe-a4ad-45c3-be25-2b021b12a5c0.svg)

After:
![after](https://user-images.githubusercontent.com/48135649/227040322-8d3f0448-18e3-4923-8187-c72df324a3fa.svg)
</details>

Fixes rust-lang#10532

changelog: [`significant_drop_tightening`]: significantly optimized
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.

2 participants