Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Also, Rust is focused foremost on correctness and end-user ergonomics, not sacrificing everything on the altar of performance like CPP. For example, the GCE and NRVO proposals for Rust didn't get traction, because their semantics and developer ergonomics are, honestly, terrible. It doesn't mean that Rust won't ever support those features in some form, but it will be a long way from now, in a different form, and it will almost certainly be opt-in syntax (so most functions likely won't use it), not an implicit change of semantics like in CPP which is easy to break accidentally.
Thus the plan is things like the large_assignments lint to detect things that need to do big stack memcpys, regardless of whether they Copy. (After all, moving [String; 100] is probably not great either, if it happens, even though it's not a copy in the Copy sense.)