riscv-zkt-list
cxx
riscv-zkt-list | cxx | |
---|---|---|
1 | 98 | |
3 | 5,559 | |
- | - | |
10.0 | 9.3 | |
almost 3 years ago | 2 days ago | |
Rust | ||
BSD 2-clause "Simplified" License | 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.
riscv-zkt-list
-
Rust Cryptography Should Be Written in Rust
> all branchless code runs in constant time
No - e.g. division is not constant time.
You have to have branchless code and only use certain instructions.
E.g. here is the list for RISC-V.
https://github.com/rvkrypto/riscv-zkt-list/blob/main/zkt-lis...
Most things except div/rem, branches and floating point are ok. Oh and obviously store/load.
cxx
-
Rust is having a positive effect in C/C++
There are cxx and autocxx, what else do you propose to do?
-
Interoperability: Swift’s Super Power
I would like to see a comparison of how this compares to Rust. In terms of interoperability it has Cxx (https://cxx.rs) to offer safe bindings to C++ but also has great support for Android, Linux and many other systems. You don't even need to hack together Windows bindings (as explained in the blog post) because Microsoft offers official bindings (https://crates.io/crates/windows). I'm not sure if I'd call it a superpower if any potential interoperability has to be written to be used (compared to it already being available). Or rather, in comparison to what is interoperability a Swift superpower? Certainly not C++ or C which can be used in a far wider set of targets.
-
Rust Cryptography Should Be Written in Rust
We selected Qt as a cross-platform solution. The C++/Rust interface is the clunkiest and ugliest part of the application, and rather complex because some state is shared between several windows in the GUI and several threads in the backend, and any component might modify that state at any time, and updates have to be transmitted to the other components without introducing inconsistencies. Using cxx [1] helped a little, though.
The project began in 2020, and I'm not sure what I'd choose as a GUI framework today – definitely not Qt Widgets, though.
[1] https://cxx.rs/
-
Link a C static library to rust cargo project
If the build process for the C library isn't too involved I recommend using cxx bridge (https://cxx.rs/) and letting cargo handle the build and linking. cxx basically allows you to describe the bidirectional interface (although it sounds like you only need 1 direction, which is fine too) in Rust code and it provides a "good enough" API for compiling C code inside the build.rs file.
-
ffizz: Build a Beautiful C API in Rust
The tooling for the first kind -- calling Rust from another language -- is a bit less developed, and tends to rely on code generation that doesn't necessarily produce a natural C API. cbindgen, uniffi, cxx, and Diplomat all take this course.
-
Best practices in creating a Rust API for a C++ library? Seeking advice from those who've done it before.
I would like to utilize OMPL's functionality in Rust code, so I want to call into OMPL C++ code somehow in Rust. I've seen two (non-mutually-exclusive) options so far: - rust-cpp, which allows you to write C++ code in Rust within the cpp!() macro. - cxx, which allows you to define both sides of the FFI boundary manually (as opposed to bindgen's automatic generation).
-
Hey Rustaceans! Got a question? Ask here (20/2023)!
I'm not sure how to do this in cxx; issues like https://github.com/dtolnay/cxx/issues/447 suggest that this isn't settled yet?
-
Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved]
I use non-vendored dependencies for the Buck build in https://github.com/dtolnay/cxx.
-
Microsoft is rewriting core Windows libraries in Rust
There's also the cpp and cxx crates for doing C++/Rust interop, but they probably aren't appropriate to use in all cases. The C ABI is definitely the safest way to go unless you're really trying to marry Rust and C++ code bases, not just writing library bindings.
-
How can I use rust libraries in C++
There's also cxx (can't vouch for it personally but it claims to make things a lot easier) https://github.com/dtolnay/cxx
What are some alternatives?
polkadot-sdk - The Parity Polkadot Blockchain SDK
cbindgen - A project for generating C bindings from Rust code
linkerd2-proxy - A purpose-built proxy for the Linkerd service mesh. Written in Rust.
rust-bindgen - Automatically generates Rust FFI bindings to C (and some C++) libraries.
nearcore - Reference client for NEAR Protocol
autocxx - Tool for safe ergonomic Rust/C++ interop driven from existing C++ headers
wgpu - A cross-platform, safe, pure-Rust graphics API.
uniffi-rs - a multi-language bindings generator for rust
solana - Web-Scale Blockchain for fast, secure, scalable, decentralized apps and marketplaces.
rust-cpp - Embed C++ directly inside your rust code!
sui - Sui, a next-generation smart contract platform with high throughput, low latency, and an asset-oriented programming model powered by the Move programming language
ritual - Use C++ libraries from Rust