ousado

> True, but it's quite natural if you think about it as an actual function (and it can be an extension method too, if desired). Note that await is not...

I really don't get why you're against supporting CPS-style (and more generally type-driven implementation selection) out of the box - without macros and additional function calls, syntactically or otherwise. We...

First of all, I don't think a different design is necessary, what's missing is a type-driven selection mechanism for async/await, and perhaps that concept could be extended to other use...

The async/await case alone is quite complex already. There's still a lot to think about: multiple returns, error handling, timeouts, parallel/throttled/sequential scheduling, perhaps even some notion of resource management. All...

Also think about error handling without exceptions. On some targets, especially cpp, exceptions are prohibitively expensive.

A testcase, even when it fails to demonstrate the problem, can still be useful to illustrate the overall setup.

This looks like a viable solution: https://stackoverflow.com/questions/41791969/is-there-a-way-to-create-an-alias-of-an-enum-value ```rust #[derive(PartialEq, Eq)] pub enum X { A, B, } impl X { pub const A1: X = X::A; } ``` "There are...

For using [rkyv](https://github.com/rkyv/rkyv) in redb, memory alignment would also be very interesting. I'd think it's sufficiently useful to make it available even if portability can't be ensured when using it.

regression: no

yes, at least for Unicode I think it would be wise to use ICU ( http://site.icu-project.org/ ) "ICU's regular expressions fully support Unicode while providing very competitive performance." Haven't looked...