Results for return_bang

AXON v1.5.1 — first crates.io publication of the AXON language full-stack runtime. Lexer/parser/type-checker/IR generator (re-exported from axon-frontend) plus the native Rust runtime: typed channels (TypedEventBus with QoS×5, π-calculus mobility, capability extrusion via shield D8 — Fase 13.f.2), Free Monad CPS handlers (Fase 2), lease kernel + reconcile loop (Fase 3+5), Epistemic Security Kernel (ESK Fase 6), Trust Types + ReplayLog (Fase 11.a+11.c), Stateful PEM over WebSocket (Fase 11.d), Ontological Tool Synthesis (Fase 11.e), Mobile Typed Channels (Fase 13). Crate publishes as `axon-lang` to mirror the Python PyPI package; library import remains `use axon::*` so existing call sites keep working unchanged.

Provides macros for getting the type of a resource, `t!(variable)` will return the type as &str

The easiest and most intuitive error handling solution.

Duck Duck Go client written in Rust

Tree-walking interpreter for clojurust (special forms, macros, destructuring)

A simple interpreted language for interfacing with Rust code

Simple command-line utility for sorting inputs by proximity to a path argument

Small, sweet, easy framework for full-stack web application

Hypothesis-like property-based testing and shrinking.

Input map for bevy

**DISCONTINUED** Please use Kurinji

Inline procedural macros

return_bang implements non-local exits for methods. As a bonus, you also get exception handling that ignores standard Ruby's inflexible begin; rescue; ensure; end syntax. Use return_bang to exit back to a processing loop from deeply nested code, or just to confound your enemies *and* your friends! What could possibly go wrong?