Skip to content

Conversation

sanxiyn
Copy link
Contributor

@sanxiyn sanxiyn commented Nov 14, 2013

This is a request for feedback. This addresses #10436, but I am not sure whether this is the right direction.

@nikomatsakis
Copy link
Contributor

I'll take a look. I have some plans to rework how trait matching works which would eliminate the idea of early vs late vtable resolution altogether. Might take me a day or two to get to it though.

@pcwalton
Copy link
Contributor

@nikomatsakis ping

@nikomatsakis
Copy link
Contributor

This doesn't seem like the right direction long term but might be reasonable short term. I have to go investigate the code a bit I guess.

@sanxiyn
Copy link
Contributor Author

sanxiyn commented Nov 29, 2013

Rebased with .. wildcard pattern change.

@sfackler
Copy link
Member

sfackler commented Jan 2, 2014

needs a rebase

@alexcrichton
Copy link
Member

Closing due to inactivity, but feel free to reopen with a rebase! (this sounds like it's a nice improvement!)

flip1995 pushed a commit to flip1995/rust that referenced this pull request Apr 6, 2023
Mini-fix `double_must_use` for async functions

From Rust 1.67 onwards, the `#[must_use]` attribute also applies to the `Future::Output` (rust-lang#100633). So the lint `double_must_use` was linting all async functions. This PR changes the `double_must_use` lint so it ignores `async` functions.

---

Closes rust-lang#10486
changelog: [`double_must_use`]: Fix false positive in async function
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.

5 participants