News for hackers. Stuff that matters.
Re:Sub-10 ms Latency in Java: Concurrent GC with Green Threads by pjmlp on Wednesday August 05, 2020 @11:26AM (#24061865)
Rust also has operator overloading and implicit conversations, both can cause memory allocations.
Re:Sub-10 ms Latency in Java: Concurrent GC with Green Threads by cogman10 on Wednesday August 05, 2020 @12:02PM (#24062305)
Certainly. However, both of those things (from what I've seen) are fairly rare.

The C++ copy constructor comes up fairly frequently.

Re:Sub-10 ms Latency in Java: Concurrent GC with Green Threads by pjmlp on Wednesday August 05, 2020 @12:10PM (#24062395)
Like unsafe Rust code, there is the theory and then there are the code bases that one finds out in the wild on crates.io and in-house, not necessarily using best practices.
Re:Sub-10 ms Latency in Java: Concurrent GC with Green Threads by dthul on Wednesday August 05, 2020 @05:35PM (#24065895)
Rust does not have implicit type conversions.
Re:Sub-10 ms Latency in Java: Concurrent GC with Green Threads by pjmlp on Thursday August 06, 2020 @02:07AM (#24068509)
Via Deref.
Re:Sub-10 ms Latency in Java: Concurrent GC with Green Threads by dthul on Thursday August 06, 2020 @02:53AM (#24068711)
Not in practice. It's only used for reference coercions to existing objects.

You would need to ignore the documentation and bend over backwards to use it for an actual type conversion, because you can only return references.

Re:Sub-10 ms Latency in Java: Concurrent GC with Green Threads by pjmlp on Thursday August 06, 2020 @03:58AM (#24068976)
Bending backwards is a synonym to code quality delivered by consulting/offshoring projects across most big corporations.