You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
catamorphism opened this issue
Jun 15, 2012
· 2 comments
Labels
A-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsI-slowIssue: Problems and improvements with respect to performance of generated code.
core::str::eq has a comment explaining that it implements string equality in Rust rather than using == in order to save a call into the shape code. It should be just as efficient to write a == b, or at least I assume that's the intent behind the FIXME.
The text was updated successfully, but these errors were encountered:
Allow implementing `Hash` with derived `PartialEq` (`derive_hash_xor_eq`
This is a common pattern and is totally allowed by the `Hash` trait.
Fixesrust-lang#2627
changelog: Move: Renamed `derive_hash_xor_eq` to [`derived_hash_with_manual_eq`]
[rust-lang#10184](rust-lang/rust-clippy#10184)
changelog: Enhancement: [`derived_hash_with_manual_eq`]: Now allows `#[derive(PartialEq)]` with custom `Hash` implementations
[rust-lang#10184](rust-lang/rust-clippy#10184)
<!-- changelog_checked -->
A-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsI-slowIssue: Problems and improvements with respect to performance of generated code.
core::str::eq
has a comment explaining that it implements string equality in Rust rather than using==
in order to save a call into the shape code. It should be just as efficient to writea == b
, or at least I assume that's the intent behind the FIXME.The text was updated successfully, but these errors were encountered: