dyntable
abi_stable_crates
Our great sponsors
dyntable | abi_stable_crates | |
---|---|---|
2 | 7 | |
16 | 491 | |
- | - | |
4.9 | 4.9 | |
12 months ago | 7 months ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
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
-
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.
abi_stable_crates
-
how can I add dynamic loading to do "plugins" for my Rust app?
I've used abi_stable_crates
-
Announcing `stabby`: a stable ABI for Rust with niche optimizations and much more!
It's possible, I even made a PR for closures a few months ago. However, for some odd reason the CI failed to build it, and months later I tried to update my PR only to find that master didn't build anymore on my machine.
-
CGlue 0.2 is out! Dynamically loadable traits in Rust, C and C++
Integration with /u/azure1992's abi_stable crate for API/ABI mismatch checking (layout_checks feature). Note that CGlue will not work with crates.io version just yet, as a certain patch needs to be published first. But in the meantime, this can be solved by specifying the upstream repo in cargo patch section.
-
What are the options of distributing a closed-source library in Rust?
There’s a crate for that: abi_stable
-
Plugin based architecture in Rust
Unfortunately, just before publishing this article I found out, that Rust does not guarante a stable ABI, not even between two separate runs of the compiler with the same rustc version. This measn that plugins might suddenly not be compatible anymore for no obvious reasons. Even though I never experienced any problems during development (neither on windows, linux nor mac), I'd recommend you to just share datastructures with #[repr(C)] attribute or use types from abi_stable_crates. A stable ABI will be shipped with minfac:0.0.2, as datastructures in minfac:0.0.1 don't have the #[repr(C)] attribute yet. A discussion about having a stable Rust ABI can be found in the internals forum. If anybody knows, why compiling with the compiler option -C prefer-dynamic is supported, I'd be interested to know, as I can't see how this problem is solved there.
-
Rust doesn’t support default function arguments. Or does it?
Here’s abi_stable_crates, enabling Rust API to be exported with a stable ABI
-
Is there a way to build a plugin system for rust code with dynamic libraries ?
This crate may also be of interest: https://github.com/rodrimati1992/abi_stable_crates/
What are some alternatives?
expand - Rust library that introduces a macro to expand byte string and string literals
interoptopus - The polyglot bindings generator for your library (C#, C, Python, …) 🐙
dynstack - A stack for rust trait objects that minimizes allocations
minfac - Lightweight Inversion Of Control
ctti - Rust compile-time type information experiment
memflow - physical memory introspection framework
waver - Waver: A waveform generation library for Rust
rust-default-arguments-benchmark - A simple benchmark to evaluate the performance impact of using structs that implement Default as function arguments.
kinded - Generate Rust enum variants without associated data
rfcs - RFCs for changes to Rust
xi-editor - A modern editor with a backend written in Rust.