I'm excited to see C++ become so powerful and intuitive. I learned C++98 during my undergrad (2016-2020) which was great, but since embracing modern C++, it's been an absolute blast
What is more intuitive and declarative this: // select all member function of // struct options auto mem_funs = select * as foo from Options where std::is_mem_function_v and std::is_public and not std::is_static; Or what was presented in the video?
I'm excited to see C++ become so powerful and intuitive. I learned C++98 during my undergrad (2016-2020) which was great, but since embracing modern C++, it's been an absolute blast
What is more intuitive and declarative this:
// select all member function of
// struct options
auto mem_funs = select * as foo from Options where std::is_mem_function_v and std::is_public and not std::is_static;
Or what was presented in the video?
27:00 how does this work? Shouldn't you need the null terminator?
The stack is probably initialized to all zero by the runtime, so the print will read out the buffer but into a 0
@_shogun Ahh. That makes sense, thank you!
Just use a simple keyword for gods sake. Unfortunately c++ is becoming an emoji language. What is next?
The problem with using keywords is that it turns what was an available identifier into a reserved word. Also, C++ != Pascal.
That would break code.
C++ already has nearly 100 keywords in addition to “identifiers with special meaning”. At some point a line has to be drawn.
@@IsaacKripkewait till you find out Swift have over 200 keywords
@metaltyphoon the COBOL standard has over 300 keywords, with some dialects having 2-3x more.