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.
-
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.
For example, The Rust compiler isn't slow; we are. and pico-args: Alternatives.
Have you tried anyhow and thiserror for making it as simple as .context("Message") or ? to type-convert and propagate errors up the call stack?
Have you tried anyhow and thiserror for making it as simple as .context("Message") or ? to type-convert and propagate errors up the call stack?
For that, placement new has been recognized as a desirable feature all along. The problem is that coming up with an implementation that doesn't require unsafe and that Rust developers are willing to commit to supporting until the end of time is harder that it looks. (See the discussions in issues like #27779 and #64062 if you want to get up to speed on how it's harder than it looks.)
A lot of that magic on the JVM (Mockito / Spring Boot) relies on proxy objects that intercept method calls, and operate on them in a non-typesafe manner (working on Object[] args, and returning Object). When you use them, it looks type-safe, but under the hood it's all dynamic. Here is an example in Mockito: https://github.com/mockito/mockito/blob/ea000f72444ed4c7e409441aedc3021951b89660/src/main/java/org/mockito/internal/creation/bytebuddy/MockMethodInterceptor.java#L59.