Some errata for C++23 Best Practices, published 2024-02-16 #368
Chris1LDN
started this conversation in
C++ Best Practices Book
Replies: 1 comment
-
Re: "strong typedef": the whole point is to get different behavior from |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
As discussed on twitter, I've been reading the C++23 Best Practices book, which I'm enjoying, but have found some issues I thought I'd share.
Page 29 - "Sanitizers can only instrument code not removed by the optimizer, but the optimizer exploits some times of UB" - possibly meant to say "some types of UB"?
Page 40 - "does not have the -fhardend flag yet" - should be "-fhardened"
Page 63 - "Exercise: Research strong typedef libraries for C++" - just a comment... not sure if the word "typedef" is best to use here since modern C++ has replaced it with "using" and newcomers might not know what "typedef" means. Maybe "strong type libraries" or "strong type system libraries"?
I'm only about half-way through but might not have time to read further for a while so thought I'd share what I've spotted so far.
Beta Was this translation helpful? Give feedback.
All reactions