Comments by "George Albany" (@Spartan322) on "Mastery Learning"
channel.
-
12
-
3
-
@Asdasdas1337
Type strictness and RAII pretty much solves all the safety problems in a simpler, more performant, and more direct fashion without making the system for less safe execution harder and less safe. (in fact RAII and type strictness can inherently make even C code more safe, as well as being trivial to compile with) Never once have I seen a safety issue personally when using C++ features properly, every time I see a safety concern, its been over some fool using C functionality in C++, like scanf, printf, strlen, or something just as unsafe and type-loose. Even more with concepts and constraints, and especially with modules coming to mostly replace header files, the only problem with the templating system in C++ will also disappear, that being that you have to do everything that isn't full types in header files. (even better that we'll no longer need declaration and definitions) Unfortunately we can't use that on every platform yet, GCC and MSVC support it but Apple's LLVM is still kinda busted, but those are merely the final conveniences on C++17, even in C++11 RAII and type strictness work perfectly fine.
1
-
@Asdasdas1337
Type strictness and RAII pretty much solves all the safety problems in a simpler, more performant, and more direct fashion without making the system for less safe execution harder and less safe. (in fact RAII and type strictness can inherently make even C code more safe, as well as being trivial to compile with) Never once have I seen a safety issue personally when using C++ features properly, every time I see a safety concern, its been over some fool using C functionality in C++, like scanf, printf, strlen, or something just as unsafe and type-loose. Even more with concepts and constraints, and especially with modules coming to mostly replace header files, the only problem with the templating system in C++ will also disappear, that being that you have to do everything that isn't full types in header files. (even better that we'll no longer need declaration and definitions) Unfortunately we can't use that on every platform yet, GCC and MSVC support it but Apple's LLVM is still kinda busted, but those are merely the final conveniences on C++17, even in C++11 RAII and type strictness work perfectly fine.
1
-
@Asdasdas1337
Type strictness and RAII pretty much solves all the safety problems in a simpler, more performant, and more direct fashion without making the system for less safe execution harder and less safe. (in fact RAII and type strictness can inherently make even C code more safe, as well as being trivial to compile with) Never have I seen a safety issue personally when using C++ features properly, every time I see a safety concern, its been over some dope using C functionality in C++, like scanf, printf, strlen, or something just as unsafe and type-loose. Even more with concepts and constraints, and especially with modules coming to mostly replace header files, the only problem with the templating system in C++ will also disappear, that being that you have to do everything that isn't full types in header files. (even better that we'll no longer need declaration and definitions) Unfortunately we can't use that on every platform yet, GCC and MSVC support it but Apple's LLVM is still kinda busted, but those are merely the final conveniences on C++17, even in C++11 RAII and type strictness work perfectly fine.
1