androidcode

4 ms·

1. 1.▲
   by androidcode 11mo ago

   no_std for instance does not protect the stack completely. That means that, if you for instance have a simple stack-overflow bug in a Rust program when using no_std, even if the program has absolutely no usage of the unsafe keyword, you can
2. 2.▲
   by androidcode 11mo ago

   Wrong, for any reasonable definition of memory safety, languages like Java and Javascript are memory safe. Java has escape hatches, but the necessity and prevalence of those escape hatches are way, way less than that of Rust. Consider for i
3. 3.▲
   by androidcode 11mo ago

   Yes, so something like a modernization profile for C++ would make it easier to enforce, and would not require external tools. But it ultimately does not change that C++ is not C, and that the blog is deeply misleading. Nor does it change th
4. 4.▲
   by androidcode 11mo ago

   BTW; Do you know if it is possible to track new comments to Hacker News threads?
5. 5.▲
   by androidcode 11mo ago

   That argument can be applied to unsafe Rust as well. There are code reviews, coding standards and other checks for a reason. Though, I suppose something like C++ profiles, just for modernization, might make it much easier to enforce and tra
6. 6.▲
   by androidcode 11mo ago

   The blog post has a number of issues, including mixing C and C++. And Android C++ source code is often filled with C-style code, especially the older the code, and is not always that good in several aspects. As an example, from https:&#x2F