Explore >> Select a destination
|
You are here 
|
without.boats | ||
| | | | |
sabrinajewson.org
|
|
| | | | | The main focus of this article will be on attempting to design a system to support asynchronous destructors in the Rust programming language, figuring the exact semantics of them and resolving any issues encountered along the way. By side effect, it also designs a language feature called async genericity which enables supporting blocking and asynchronous code with the same codebase, as well as designing a system for completion-guaranteed futures to be added to the language. | |
| | | | |
blog.yoshuawuyts.com
|
|
| | | | | ||
| | | | |
theincredibleholk.org
|
|
| | | | | There are currently two competing designs for async iteration traits for Rust. The first is poll_next. The second is async fn next. I see strengths to each desi... | |
| | | | |
www.adamalbrecht.com
|
|
| | | UPDATE: There have been some changes in the JWT Gem that make some of the below not work exactly right (it'll still be about 90% the same). Specifically, they added expiration support. See my post on the same topic, but using React.js. The server side code in this post will work just as well with Angular. | ||
