dyntable
Idiomatic and FFI Safe dyn traits in Rust (by outfoxxed)
ctti
Rust compile-time type information experiment (by h33p)
Our great sponsors
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dyntable
Posts with mentions or reviews of dyntable.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-24.
-
Announcing `stabby`: a stable ABI for Rust with niche optimizations and much more!
I've been writing something pretty similar for a few months. Glad to see I'm not the only one who wants to fix the abi problem.
-
dyntable: FFI safe traits with almost the full featureset (seeking review)
The repo is here.
ctti
Posts with mentions or reviews of ctti.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-15.
-
"Serialize" type info to a runtime tag based on serde data model.
This is inspired from ctti crate https://github.com/h33p/ctti from https://blaz.is/blog/post/we-dont-need-a-stable-abi/ I think this type tag may work as an alternative to stable typeid.
-
Announcing `stabby`: a stable ABI for Rust with niche optimizations and much more!
Awesome work! I looked through your code and it seems like you are building your own form of type information. One of my proposals was to put type information generation inside the compiler. Here's a crate showing how it could look: https://github.com/h33p/ctti
What are some alternatives?
When comparing dyntable and ctti you can also consider the following projects:
expand - Rust library that introduces a macro to expand byte string and string literals
abi_stable_crates - Rust-to-Rust ffi,ffi-safe equivalents of std types,and creating libraries loaded at startup.
dynstack - A stack for rust trait objects that minimizes allocations
rust - Empowering everyone to build reliable and efficient software.
waver - Waver: A waveform generation library for Rust
serde-typeinfo - "Serialize" type info to a runtime tag based on serde data model.
kinded - Generate Rust enum variants without associated data
rfcs - RFCs for changes to Rust
Constime - Zig's comptime for Rust. Mostly something to play around with until more stuff is `const` fn.