abi_stable_crates
minfac
abi_stable_crates | minfac | |
---|---|---|
7 | 1 | |
491 | 23 | |
- | - | |
4.9 | 0.8 | |
7 months ago | about 1 year ago | |
Rust | Rust | |
Apache License 2.0 | MIT License |
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.
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/
minfac
-
Plugin based architecture in Rust
Creating a microframework on top of minfac is straight forward. The following sections illustrate the takeaways when building the prototype. The workspace has the following structure:
What are some alternatives?
interoptopus - The polyglot bindings generator for your library (C#, C, Python, …) 🐙
kangaru - 🦘 A dependency injection container for C++11, C++14 and later
memflow - physical memory introspection framework
dilib-rs - A dependency injection library for Rust
rust-default-arguments-benchmark - A simple benchmark to evaluate the performance impact of using structs that implement Default as function arguments.
Autofac - An addictive .NET IoC container
ctti - Rust compile-time type information experiment
Simple Injector - An easy, flexible, and fast Dependency Injection library that promotes best practice to steer developers towards the pit of success.
xi-editor - A modern editor with a backend written in Rust.
container - A lightweight yet powerful IoC dependency injection container for the Go programming language
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
eavesdropper - A CLI tool that captures packets and utilizes plugins to analyze packet information via a shared database.