|
@shafikyaghmour | |||||
|
I am excited to have written:
P1705R0
“Enumerating Core Undefined Behavior”
open-std.org/jtc1/sc22/wg21…
#cplusplus pic.twitter.com/fqbcrcEFPk
|
||||||
|
||||||
|
Shafik Yaghmour
@shafikyaghmour
|
2. srp |
|
There were four examples of undefined behavior that sound crazy in the introduction.
Here are references for them:
- Time travel undefined behavior: devblogs.microsoft.com/oldnewthing/20…
- bool both true and false: markshroyer.com/2012/06/c-both…
- Removing safety checks: blog.regehr.org/archives/970 pic.twitter.com/Oxzhnko9QS
|
||
|
|
||
|
Shafik Yaghmour
@shafikyaghmour
|
2. srp |
|
- Turning finite loops infinite: stackoverflow.com/q/32506643/170… and stackoverflow.com/q/24296571/170… pic.twitter.com/JAMJkE7CFL
|
||
|
|
||
|
Shafik Yaghmour
@shafikyaghmour
|
17. lis |
|
Revision 1(R1) of this proposal: twitter.com/shafikyaghmour…
|
||
|
|
||
|
Krystian
@crythesly
|
2. srp |
|
This seems like a near impossible task... Things can be UB by omission, and catching all those cases would be near impossible.
|
||
|
|
||