Comment thin on details (Score 1) 121
I watched the 20 minute presentation. Very thin on details. The gist was that enum cases are not flagged in ensure one has all cases covered. I have not used C++ in 20 years (probably lots of changes). I coded up an example with a switch statement and got a warning from clang/llvm C++ version 13.0.0 that not all cases in my switch were handled. So, I am not seeing any specific on how rust is better. The only useful information that I got is that the rust develop feel more productive according to google surveys. The real way to compare would be to have a C++ team and a rust team of equal capability and have 50% of traffic go to C++ and 50% of traffic go to rust code. Both teams would start with no code. Then lets compare bugs and maintenance cost. That being said I suspect that C++ have many more dangers; however, is there not a subset of C++ that one can stay within to keep the code "save"? I did not have the time to go through the thread where Stoustrup seems to think so: https://developers.slashdot.or... If C++ can have a flag for a "safe" or "safer" mode, I think that could be a major breakthrough.