by awesomekling on 5/9/24, 5:13 PM with 17 comments
by coffeeaddict1 on 5/9/24, 7:08 PM
However, I'm afraid that the ISO C++ group is not ready for his proposal. We're talking about a committee which has stubbornly and consistently shown that they are willing to sacrifice safety and ergonomics in the name of backward compatibility. The introduction of a borrow checker is a huge change that will get shut down because someone somewhere is unwilling to rewrite their (often broken) code and/or compile their binaries again.
by rogerclark on 5/9/24, 6:49 PM
Buy the compiler, get somebody who could build you a nuclear reactor, drug discovery simulator and a GPU architecture. Deal of the century.
by pjmlp on 5/9/24, 6:17 PM
Too much infrastructure code and industry standards, that will be kept being done in C++ for decades to come, and need a way for improving the whole security story.
by PaulDavisThe1st on 5/9/24, 7:44 PM