[dead]
1. This seems like it's be far too tricky and make C++ even more footgunny, especially with references, move constructors, etc etc. 2. Name lookup and overload resolution is already so complex though! This will likely…
Your comment makes no sense. If it was designed for non-null terminated strings, why would it specifically pad after a null terminator? I looked up the actual reason for its inception: --- Rationale for the ANSI C…
Sounds like a problem with poor code rather than something unique to OOP.
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
1. This seems like it's be far too tricky and make C++ even more footgunny, especially with references, move constructors, etc etc. 2. Name lookup and overload resolution is already so complex though! This will likely…
[dead]
[dead]
[dead]
[dead]
[dead]
Your comment makes no sense. If it was designed for non-null terminated strings, why would it specifically pad after a null terminator? I looked up the actual reason for its inception: --- Rationale for the ANSI C…
[dead]
Sounds like a problem with poor code rather than something unique to OOP.
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]