hotjump · HackerTrans

The problem of C code migration to memory safe languages is that legacy C projects aim for extremely high performance. Garbage-collecting languages would also be safe in any situation, but I want to note that the recent tendency toward Rust derives from its type-system based approach that imposes very few runtimes checks such as bound checking. I myself hope something like F* gets more attraction in the industry.

hotjump

last yeardiscuss

"Rust memory management explained" (excluding borrowing) is TBH wild. Without borrow checker Rust safety guarantee is nothing new

hotjump

3 years agodiscuss

I'm japanese.TBH for a long time i had thought this was a parody account. Around the time of 2011 3.11 earthquake, the NERV Twitter account(the origin of this app) gained popularity and reputation as a reliable source of information in the social media space (At that time government official information provided on Twitter was extremely little).

I guess a part of the reason of its popularity today belongs to otaku culture on the Internet that was a good fit for this kind of anime-origin stuff. Plus the company that runs NERV is owned by Sakura-Internet, which is one of the biggest computer infra business, and is believed to provide a reliable system at time of emergency.

hotjump

3 years agodiscuss

I'm a junior in uni, and I hate it when I say "Yeah we learned this technique in the C class, but it's UB in C++ so please rewrite that" in reviewing friends' codes that do type-punning with unions. So I'm also very happy with the 'std::bit_cast' in general.

BTW how about std::is_constant_evaluated()? I assumed it would help folks who do heavy physics simulations, but looks like not listed in the article.

comments