Search Results for "structs"

wasm-bindgen is a foundational Rust tool that enables seamless interoperability between Rust and JavaScript by generating the necessary bindings and glue code for WebAssembly modules. It allows developers to write performance-critical code in Rust, compile it to WebAssembly, and then expose functions, structs, and APIs directly to JavaScript in a natural and idiomatic way. The tool automates the process of bridging differences between Rust’s type system and JavaScript’s dynamic environment, making cross-language integration significantly easier. One of its key design principles is efficiency, following a “pay only for what you use” model where only the required bindings are generated, minimizing unnecessary overhead. ...

...All engine and game logic uses Bevy ECS, a custom Entity Component System. Massively Parallel and Cache-Friendly. The fastest ECS according to some benchmarks. Components are Rust structs, Systems are Rust functions. Queries, Global Resources, Local Resources, Change Detection, Lock-Free Parallel Scheduler. Bevy is still in the very early stages of development. APIs can and will change (now is the time to make suggestions!). Important features are missing. Documentation is sparse. Please don't build any serious projects in Bevy unless you are prepared to be broken by API changes constantly. ...

CXX is a library that offers safe interop between Rust and C++. It provides a safe mechanism for calling C++ code from Rust and vice versa, one that is protected from the many possible things that can go wrong when bindgen or cbindgen is used to generate unsafe C-style bindings. The general idea of CXX is to define the signatures of both sides of the FFI boundary embedded together in one Rust module. CXX gets a complete picture from this of the boundary, and through it is able to perform...

This is a Rust crate that provides a convenient derive macro (#[derive(Error)]) for implementing std::error::Error on your custom error types (structs or enums). The goal is to enable library authors to build expressive, typed error types, with readable Display implementations (via #[error("...")] annotations) as well as From conversions (#[from]), source tracking (#[source]), and optionally backtraces. It is designed so that switching from handwritten error implementation to using this error is not a breaking change: you retain the same API. ...

...JSON is a very loose format where anything goes - arrays can hold mixed types, object keys can change types between API calls or not include some keys under some conditions. Mapping that to idiomatic Rust structs introduces friction.