Don't warn about instantiating a copy type parameter with a non-implicitly-copyable type when the receiver is the only one with the type parameter #2542
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
A-lints
Area: Lints (warnings about flaws in source code) such as unused_mut.
A-type-system
Area: Type system
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
Comments
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Jul 17, 2020
Closes rust-lang#2277 This was fixed when we fixed rust-lang#2542.
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Jul 17, 2020
Add test for `needless_range_loop` issue Closes rust-lang#2277 This was fixed when we fixed rust-lang#2542. changelog: none
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Sep 22, 2022
celinval
pushed a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
This allows users to write their own custom visualization script to run after running the benchmarks. Prior to this commit, visualizations had to be checked into the Kani repository. When run_command is specified as a visualization, benchcomp runs the specified command and passes the result of the run as a JSON file on stdin. The command can then process the result however it likes. This resolves rust-lang#2518.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
hashmap.contains_key("foo")shouldn't warn, because the type parameters are only in the receiver.The text was updated successfully, but these errors were encountered: