Our great sponsors
-
wg-allocators
Home of the Allocators working group: Paving a path for a standard set of allocator traits to be used in collections!
-
-
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.
-
zenoh
zenoh unifies data in motion, data in-use, data at rest and computations. It carefully blends traditional pub/sub with geo-distributed storages, queries and computations, while retaining a level of time and space efficiency that is well beyond any of the mainstream stacks.
-
-
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.
Tracking issue for Storages, and a TLDR on what it is
Most importantly, the stabby type representation is now specified: You can now actually read how stabby represents your types. You can even implement that representation in your language of choice, and be able to interract with types defined in Rust by stabby. If I ever get brave enough, I might try to implement stabby for C++, but I make no promises. stabby's code has been validated to actually use that representation.
Zenoh's plugin system was one of the main motivators for building stabby. However, Zenoh needs me on other fronts at the moment, so stabby will have to go to the back burner for a bit. This doesn't mean stabby will become unsupported: if you want to use it, and are having a hard time, feel free to DM me to get some support. In fact, what stabby needs most right now is feedback on what types you'd like to see supported, so go for it!
You could possibly use the PoC as a basis on stable
The problem with all current solutions is that if you want to have a stable ABI for something, all of that thing's dependency must have explicitly opted into a stable ABI themselves. For some features of Rust, like the Wakers that allow futures to run, this is downright impossible, since the stdlib would need to accept either a breaking change, or a performance regression for all futures as calling convention adaptors would need to be added. I'm trying to address that one with the Generic Futures, but there will be some roadblocks on that one.