Vrtgs
Vrtgs
> rx.recv().expect("spawned task should be able to be scheduled properly") > Here `spawn_blocking` will return immediately. This effectively makes the `Drop` being concurrently with other `Drop`. This might break some...
> I think it should blocking because it is blocking in other branches, no? well, the reason it blocks in other branches is because it can, one case is its...
looking forward to it!
any updates on this?
consider [nbyte-int](https://github.com/vrtgs/nbyte-int) (or on [crates.io](https://crates.io/crates/nbyte-int)) for the u24/u48 integers, please open issues on any functionality you may need I will try to help
or actually, can you make the public API use std::time::Duration, and convert internally using `https://doc.rust-lang.org/std/time/struct.Duration.html#method.as_millis` and then `u64::try_from(milis).ok()`
Sorry to do this yet again but I think it would make more sense that you use `u64::try_from(milis).ok().unwrap_or(u64::MAX)` (or just copy the stdlib but with u64, whichever you prefer) as...
I know this might be very blame-y but reqwest just doesn't work in wasip1, it uses wasmbindgen to hook into JS, so you should just not use the default reqwest...
fixed, the issue was, for some reason this project uses both async-std executor as well as futures executor, so when I purged just async-std that wasn't enough