Explore >> Select a destination
|
You are here 
|
boats.gitlab.io | ||
| | | | |
smallcultfollowing.com
|
|
| | | | | [AI summary] A developer explains the technical challenges of ensuring async trait functions return Send futures in Rust and proposes a syntax solution where function callers specify send requirements rather than enforcing them globally in the trait definition. | |
| | | | |
theincredibleholk.org
|
|
| | | | | Lately I've been talking to a few people about whether it might be possible to replace the Pin wrapper in Rust with a new Move trait. Pin is one of those things... | |
| | | | |
leshow.github.io
|
|
| | | | | Unless you've been living under a rock; you know async/await is coming to rust stable. My last post was about implementing a simple protocol using manual futures, and interacting with tokio. It's only fitting, then, that I update the lib that post was inspired by to async/await and report back on my findings. If you're curious about my library or you use the window manager i3, it's available here or on crates under tokio-i3ipc. | |
| | | | |
boats.gitlab.io
|
|
| | | Today I realized a new crate called pin-cell. This crate contains a type called PinCell, which is a kind of cell that is similar to RefCell, but only can allow pinned mutable references into its interior. Right now, the crate is nightly only and no-std compatible. How is the API of PinCell different from RefCell? When you call borrow_mut on a RefCell, you get a type back that implements DerefMut, allowing you to mutate the interior value. | ||
