News for hackers. Stuff that matters.
Re:Four Years of Rust by pjmlp on Wednesday May 15, 2019 @04:26PM (#19923390)
Only to the GC hating crowd.

Unreal and UWP/COM developers are perfectly fine with writing C++ code with a GC around.

Re:Four Years of Rust by pornel on Wednesday May 15, 2019 @05:31PM (#19923973)
If GC & runtime is on the table, then there are many nicer languages you can use (Go, D, Swift, Kotlin). I assume that the C and C++ users who haven't switched yet are largely the "GC-hating" crowd that can't.

COM and other refcounted ones get a pass. But I'm surprised that Unreal gets away with a mark-and-sweep GC. Perhaps because it's only required for UObjects, and the rest of the codebase can still easily avoid using the GC? You can even cause use-after-free bugs on UObjects, if you want to.

Re:Four Years of Rust by sanxiyn on Wednesday May 15, 2019 @11:56PM (#19926010)
Isn't Swift also refcounted?
Re:Four Years of Rust by pjmlp on Thursday May 16, 2019 @12:32AM (#19926137)
Reference counting is a GC algorithm, as per CS curriculum.
Re:Four Years of Rust by renox on Wednesday May 15, 2019 @06:11PM (#19924282)
Try to broaden your horizons.. I work in telecoms only one step away from a FPGA, a 1ms pause would be a critical bug report..
Re:Four Years of Rust by pjmlp on Thursday May 16, 2019 @12:25AM (#19926105)
My horizons are already broaden.

https://atlas.cern/discover/detector/trigger-daq

You can also try to broaden yours.

https://www.ptc.com/en/products/developer-tools/perc

Will this work for you? I guess most likely not, and you really cannot afford any kind of delay, where even a C++ virtual call would be considered a bug, given the 1ms delay.

The point being that only a very tiny population has such requirements, just like barely anyone writes applications 100% fully in Assembly.

Re:Four Years of Rust by renox on Sunday May 19, 2019 @01:19PM (#19954322)
I'll look at your links but to answer to your question: yes virtual functions are not accepted in the code.