mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Rollup merge of #105522 - est31:remove_or_and_note, r=scottmcm

Browse Source 
Remove wrong note for short circuiting operators

They *are* representable by traits, even if the short-circuiting behaviour requires a different approach than the non-short-circuiting operators. For an example proposal, see the postponed [RFC 2722](https://github.com/rust-lang/rfcs/pull/2722). As it is not accurate, remove most of the note.
This commit is contained in:
Matthias Krüger 2022-12-10 09:24:45 +01:00 committed by GitHub
commit f6c2add0ed
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
library/core/src/ops/mod.rs
View File

@ -17,10 +17,10 @@
//! should have some resemblance to multiplication (and share expected //! should have some resemblance to multiplication (and share expected
//! properties like associativity). //! properties like associativity).
//! //!
//! Note that the `&&` and `||` operators short-circuit, i.e., they only //! Note that the `&&` and `||` operators are currently not supported for
//! evaluate their second operand if it contributes to the result. Since this //! overloading. Due to their short circuiting nature, they require a different
//! behavior is not enforceable by traits, `&&` and `||` are not supported as //! design from traits for other operators like [`BitAnd`]. Designs for them are
//! overloadable operators. //! under discussion.
//! //!
//! Many of the operators take their operands by value. In non-generic //! Many of the operators take their operands by value. In non-generic
//! contexts involving built-in types, this is usually not a problem. //! contexts involving built-in types, this is usually not a problem.