This is not

Like what you see? Install OctoLinker now!

Skip to content


Here are 1,483 public repositories matching this topic...

njsmith commented May 18, 2020

What should happen if deliver_cancel raises an exception? In the current implementation, the shielded cancel scope will prevent it from propagating until the process exits, which might take a while if the crash occurred before signaling the process in any way. Maybe on exception from a user-specified deliver_cancel we should call the default deliver_cancel to kill the process? Or just kill() since

taiki-e commented Feb 5, 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,

enhancement good first issue
mfvargo commented Jan 22, 2021

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:


good first issue enhancement help wanted

This is a basic API REST skeleton written on JavaScript using async/await. Great for building a starter web API for your front-end (Android, iOS, Vue, react, angular, or anything that can consume an API). Demo of frontend in VueJS here:

  • Updated May 4, 2022
  • 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.

Curate this topic

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."

Learn more