-
Updated
Apr 12, 2021 - Python
async-await
Here are 1,082 public repositories matching this topic...
-
Updated
Apr 9, 2021
Most of async-std's stream utilities were written before Stream::size_hint was released and do not implement Stream::size_hint method. This means that async-std's stream utilities may be a bit inefficient than other crates such as futures, tokio-stream, futures-lite, which provide similar utilities.
related: rust-lang/futures-rs#1853, https://github.com/rust-lang/rus
We had an issue where an api user was using the incorrect parameters on an API call. Having this feature would have made the API fail instead of proceeding. The bug would been found earlier.
I can see where this would be a hassle on many cases, But it would be nice for new projects.
I suppose it could be a global config item that could be overridden at the individual action level:
For
-
Updated
Feb 14, 2021 - JavaScript
-
Updated
Mar 9, 2021 - TypeScript
-
Updated
Oct 31, 2018 - HTML
-
Updated
Apr 3, 2021 - C#
-
Updated
Feb 28, 2021 - C++
-
Updated
Mar 4, 2020 - JavaScript
-
Updated
Apr 13, 2021 - Rust
-
Updated
Dec 9, 2020 - Java
-
Updated
Jul 30, 2019
-
Updated
May 15, 2020 - Swift
-
Updated
Mar 31, 2021 - Vue
-
Updated
Oct 31, 2018 - JavaScript
-
Updated
Apr 14, 2021 - TypeScript
-
Updated
Feb 1, 2021 - Swift
-
Updated
Jan 23, 2021 - JavaScript
-
Updated
Mar 30, 2021 - JavaScript
-
Updated
Mar 9, 2021 - JavaScript
-
Updated
Mar 24, 2021 - JavaScript
-
Updated
Jul 16, 2020 - JavaScript
-
Updated
Mar 29, 2021 - TypeScript
-
Updated
Apr 12, 2021 - Python
-
Updated
Mar 27, 2021 - C++
-
Updated
Jun 4, 2017 - JavaScript
Improve this page
Add a description, image, and links to the async-await topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the async-await topic, visit your repo's landing page and select "manage topics."
This is the core part of the loop that our worker threads currently run:
https://github.com/python-trio/trio/blob/6b0a094c8e5860ff5e26e825ff867229bf9707bb/trio/_core/_thread_cache.py#L60-L73
You can see that we currently explicitly
del fnanddel deliver. That's because these are two arbitrary user objects, and if we didn't delete them, then they would stick around until the worker threa