Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
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.
I will add, that, as it stands, I'm not using time anymore, as it does not yield an improvement compared to just using std::time for me. While the documentation of time mentions "[...] serde support for all types", it doesn't actually implement Serialize and Deserialize for its Instant type, which leaves me with the same situation as std::time::Instant. Having read this issue carefully, I think that makes sense now. Thus, now I'm just storing the elapsed time from an Instance created before my measuring loop, which gives me a Duration that can be serialized.
For a specific example: I am interested in working with 3D objects using Rust (maybe this is too ambitious for a newbie!) so I found a CAD kernel crate called truck which seems to be crate built of smaller crates and implementations of other libraries. How would you go about finding the most relevant info and where to start? Should I start by understanding all the smaller parts such as the gui/gpu rendering modules, or is that irrelevant and I can focus on figuring out the top level?
For context, I’m working on an ignore_if RFC and I’m trying to understand reasoning for the syntax.
It was changed in 1.34 (https://github.com/rust-lang/rust/pull/57367).