Hopefully Java will support proper values regarding inlining and on-stack allocation for non-primitive types soon, but yes option types are a benefit in Rust as long as you’re not using any more advanced reference libraries.
Haven’t really seen anyone trying to use JVM options to get performance benefits without benchmarks for their specific use case the last 10 years or so.
No offense to Tokio and Rust, I really like Rust, but having someone rewriting their app because of performance limitations in their previous language choice, isn’t really someone picking the right tool for the job necessary.
I’m not so sure they would have done the rewrite if the Go GC was performing better, and the choice of Rust seems primarily based on prior experience at the company writing performance sensitive code rather than delivering business value.
Trolling is fun and all, but I wouldn’t say Rust’s type system that much more advanced than Java’s. The borrow checker definitely helps to catch errors, but I would rate them at basically the same level.
They are not that similar to a struct in C in that they are not just about being a data carrier. So that might be confusing if that is what you expect.
Future work is intending to solve the third point and add deconstructing the record for pattern matching.
“We can declare a simple x-y point abstraction as follows:
record Point(int x, int y) { }
which will declare a final class called Point, with immutable components for x and y and appropriate accessors, constructors, equals, hashCode, and toString implementations.”
Would dependent types help in this case?
Add the reference type when creating the type and then you could have the compiler check that the contract holds.
They are still allowed to have police present at the internal border and checking both your id, itinerary and asking questions about your visit as long as it’s not “systematic”.
Yeah, having reads rebalancing the tree in a multithreaded subsystem is probably not optimal. Might be that the Splay-trees have outstayed their welcome :)
FreeBSD’s tree.h used to have, iirc, both RB- and Splay-trees.
Sexier name for sure.
We do still call the age before the current Nordic states were established the age of Vikings in Sweden.
The whole notion of Vikings being stupid and naive sounds very old fashioned. The whole idea that short seasons and snow would scare off any people from the Nordic countries is bullshit. Nuuk is at 64 degrees north, roughly similar to Reykjavík, Trondheim or the southern point of the northern third of Sweden. Which had been inhabited for much longer. The climate is slightly better in Scandinavia that far north, but Greenland would surely have been similar.
Unfortunately that seems to be common. Artifactory for example has similar requirements. Guessing that running full free text search and analysis on the artifacts are the main culprits.