Our great sponsors
-
containers
My attempt at reimplementing some of the rust standard containers, starting with a doubly linked list (by SKyletoft)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
gutenberg
A fast static site generator in a single binary with everything built-in. https://www.getzola.org
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
This is the code that handles the allocation
Thanks, that's exactly what I was looking for. Though if I'm reading the linked tracking issue correctly, the new preferred way is to use the syntax added by this PR:
nushell is a super welcoming project that seeks to build a better shell in Rust. The discord server is super friendly, and they're generally happy to mentor.
I'm way ahead of you. I found out about it because I noticed the impl Clone for Pool at the bottom and clicked the [src] button to verify that the pool was shared among clones.
Another place they are useful is repetitive impl blocks. Finally I've also sometimes used them as a short-hand for a certain kind of expression I write a lot, e.g. this test.
I think I'm understanding where you're going, but still can't get it to work. I started with this idea here. I get this error:
I find myself repeating myself between crate-level doc comments and README files. What are people using to avoid that? cargo-readme + a CI hook?
Related posts
- Hey Rustaceans! Got an easy question? Ask here (15/2021)!
- Top 10 Rusty Repositories for you to start your Open Source Journey
- Show HN: Game of Life with grid editor in browser with Rust and WASM
- Recreating the Apple Calculator in Rust using Tauri, Yew and Tailwind
- Yew: Rust / WASM framework for creating reliable and efficient web applications