In #Tauraro by default Ownership and borrowing is auto infered + Automatic Reference Counting (ARC).
BUT you can still optionally opt-in for explicit ownership/borrowing/lifetime to achieve Rust style zero-copy π₯π₯π
Just use --strict compiler flag π₯π
In #Tauraro you can opt-in to Rust style borrow checker and lifetime to benefit to 100% zero-copy without the Tauraro ARC (Automatic Reference Counting) that add a little more memory usage overhead
Benchmarks, WataX vs Rust Axum π₯:
https://t.co/sI0UCMOIML
Download:
https://t.co/694linWIYx
Follow this link to join the community and start building : https://t.co/sz03YM70gh
The Tauraro ecosystem just got faster! πππ₯π₯π₯
Introducing watax a high-concurrency web framework built for Tauraro that delivers best-in-class performance and memory efficiency. Perfect for high-traffic applications.
Repo:
https://t.co/Ds2dv0qqDR
β Comprehensive benchmark suite covering 10 workloads including Fibonacci, Mandelbrot, N-body simulation, matrix multiplication, and more.
π Major bug fixes eliminated memory leaks (including reducing some cases from *16MB to 0MB*) and improved overall performance.
π *Tauraro v0.0.6 Released!*
A major update focused on *performance, memory safety, concurrency, and interoperability*.
β¨ check comments:
https://t.co/rAZtUk2cJJ
β οΈ Enhanced type system with better tuple and collection support.
β Smarter compiler analysis to prevent double-free and use-after-free issues.
β High-performance HTTP server improvements and scalable I/O
I prefer #Tauraro than Rust for VibeCoding, if you VibeCode in Tauraro and you're hitting a bug then you have no headache in manual debugging and fixing errors, for it have simple Python like syntax
β οΈπ₯ππ―π€
@TauraroLang
We have to release #Tauraro v0.0.5 on purpose this early.
It's a huge features transformations and more stable release π₯π―π
the previous release v0.0.4 comes with #taupkg but v0.0.5 will comes with #Templa (jinja2 like templating engine) and #Tauraro_LSP for IDEs