[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…
As a c++ developer who's heard of Zig but never dived into it, I was reading this article scratching my head wondering what is it actually so unique about it. Why the blog has a section on how it install it on the path…
Sounds like a problem with poor code rather than something unique to OOP.
[dead]
[dead]
[dead]
[dead]
[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]
[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…
As a c++ developer who's heard of Zig but never dived into it, I was reading this article scratching my head wondering what is it actually so unique about it. Why the blog has a section on how it install it on the path…
[dead]
Sounds like a problem with poor code rather than something unique to OOP.
[dead]
[dead]
[dead]