async-await

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

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

When the user saves a form it'd be nice to see some kind of visual feedback about what happened, instead of just reloading the page. The edit form notification box should be enabled by default for all the edit forms.