Safer C++ - Better C++

C++ is having trouble. Governments and huge corporations are moving quickly to transition to memory-safe languages.
But that’s not always an option, so we have to fight to improve our C++ toolchains and language bases.
In this episode, I want to share my thoughts about improving code (mainly C++, not only).
Some are in development, and some already exist. If you are interested in programming, especially for embedded systems.
Improve code quality and efficiency for better programming results!
I hope you enjoy that episode! And don't forget to share your thoughts in the comments!
Repositories:
github.com/rdipardo/vim-cpywrite - my fixes already delivered
github.com/hsutter/cppfront - my fixes delivered, but without modules
github.com/matgla/cppfront - modules on basicModulesSupport branch
github.com/matgla/dotfiles - dotfiles, vim configuration in common branch
github.com/modern-cmake/cppfront - idea of filtering h2/cpp2 files
Chapters:
00:00-00:45 Intro
00:45-03:17 Should we abandon C++?
03:17-05:18 Rust is not a solution for me ☹
05:18-12:04 Let’s make C++ great again!
12:04-15:18 Modules, why do you take so long?
15:18-18:07 Why defaults are so hard?
18:07-20:32 Analyze runtime in compile time
20:32-21:53 Wash your hands - sanitizers
21:53-22:45 How to break it? - tests
22:45-23:59 Make space for more code!
23:59-24:33 Guidelines, don’t need to follow, but at least know them!
24:33-25:00 Outro
Used others materials from:
www.digitaltrends.com/computi...
www.nsa.gov/Press-Room/News-H...
/ google-grants-1-millio...
www.zdnet.com/article/microso...
medium.com/@techhara/why-c-c-....
codeandhack.com/google-first-...
stackoverflow.blog/2019/11/14...
www.behance.net/gallery/42774...
llvm.org/Logo.html
archive.org/details/amiga_wor...
isocpp.org/home/terms-of-use
commons.wikimedia.org/wiki/Fi...
en.wikipedia.org/wiki/File:Bj...
blog.rust-lang.org/2015/04/24...
blog.rust-lang.org/2015/05/11... - :~:text=Abstraction%20without%20overhead%3A%20traits%20in%20Rust%201%20Background%3A,where%20all%20abstraction%20is%20compiled%20away%20statically.%20
doc.rust-lang.org/book/ch16-0... - :~:text=We%E2%80%99ve%20nicknamed%20this%20aspect%20of%20Rust%20fearless%20concurrency.,being%20more%20precise%20by%20saying%20concurrent%20and%2For%20parallel.
blog.rust-lang.org/2015/04/17...
• How to draw the Mona L...
gcc.gnu.org/bugzilla/show_bug...
gcc.gnu.org/bugzilla/show_bug...
github.com/bnoordhuis/v8-cmak...
github.com/tdlib/td/issues/334
github.com/leggedrobotics/dar...
blog.csdn.net/qq_45657288/art...
forums.developer.nvidia.com/t...
clang.llvm.org/extra/clang-tidy/
www.robotics-university.com/2...
www.ti.com/tool/CCSTUDIO
Cat with steampunk glasses: Designed by Freepik www.freepik.com/free-ai-image...

[@siman211]

Can you recommend a course to learn c++ with 0 programming knowledge?

[@matgla95]

Hi! I was teaching myself around 16 years ago. Back then I was using some random c++ course in my native language. I think most important is to spend a lot of time doing exercises. Starting from basics means firstly you need to learn the programmer's way of thinking and problem solving starting from really basic and simple programs. C++ is quite a complex language to learn, but patience and consistency will pay off in the future.

[@user-qt5hy3vn5p]

Safer C++? Rust?

[@matgla95]

That's only my personal opinion and to say it loud: I have no Rust experience, only years of experience in c++. I did some research that made me think that using Rust it's harder to write unsafe code in some areas ( i.e. memory safety, thread safety ) as opposed to C++. But still in any language you can write unsafe code and in any language you can write safe code (even in assembly or brainf**k, but with more effort spent and easier to introduce buggy unsafe code by mistake). And that covers just language level safety. I think that a much harder point is to implement the whole software architecture as a safe which is more crucial. Maybe we have someone here with both C++ and Rust experience? I am curious about her/his view :)