* Minor comment fix
* Minor language fix
* Minor language fix
* Minor clarification
* Minor language fix
* Minor language fix
* Remove whitespace for clarity
* Make whitespace consistent (again, it wasn't the "bad" here, right?)
* Minor language fix
* Change weird formatting for emphasis
* Fix (what I believe is) a slightly distracting typo
* Minor language fix
* Suggest to highlight even security vulnerabilities as a possible outcome of concurrency errors
* Minor language fix
* Suggest to add new section for a seemingly unrelated note
* Minor language fix
* Minor language fix (not sure what this intended to say in the first place?)
* Minor language fix
* Add minor remark
* Minor language improvement
* Minor language fix
* Point out a bad example
* Minor fixes
* Minor language fix
* Add missing period (the lack of which doesn't look bad here, but does a bit in the rendered html)
* Minor language fix
* Minor language fix
* Minor typo fix (but is this what was meant?)
* Minor language improvement (?)
* Minor language fix
* Minor language fix (?)
* Add missing closing quotation mark
* Minor language fix
* Minor language fix
* Remove extra dot (or was it supposed to be three dots instead?)
* Minor language fix
* Minor language fix
* Minor language fix
* Minor language fix
* Minor language improvement
* Minor formatting improvements
* Minor improvements
* Minor language fix
* More fixing
* Add missing parentheses (did I get it right?)
* Minor language fix (?)
* Minor language fix
* Minor language fix
* Fix language (but is this what was meant in the first place?)
* Update heading to match content (in particular, the example)
* Remove superfluous whitespace
* Update also the "bad" example to use int*
* Add '<=>' to comparison operators related rules (C.87, C.167)
C++20's three-way comparison operator should respect the same rules as other
comparison operators.
* Fix a minor typo
Co-authored-by: Jonathan Wakely <github@kayari.org>
Co-authored-by: Jonathan Wakely <github@kayari.org>
This allows the example to remain simple well not misleading a beginner
such a comparison is safe. Including an epsilon comparison or something
similar would overly complicate this example.
Co-authored-by: Martin O'Shea <martin.oshea@native-instruments.com>
* Update C.83 with swap for resource mgmt.
The swap is useful to implement assignments idiomatically (e.g. copy-swap idiom).
With the current enforcement, to non-virtual classes, very simple classes (e.g. `trivially_copyable`, a struct encapsulating an stl container) are suggested to have a swap. This suggestion can be argued wrong since for very simple classes copy-swap idiom is not efficient (the creation of a third object on assignment is not needed, which copy-swap does).
* Rework C.83 according to PR comments.
Herb Sutter
Juha Reunanen
Bill Rose
Kie
Sergey Zubkov
nullptr-cpp
Martin
JuliusBrueggemann
syntroniks
shaneasd
Florian Behrens
peno2
David Leal
Niels Dekker
Fernando J. Iglesias García