Léo Gaspard

Option 4: like option 3, but also introduce a leap second table (potentially fetched from the system) to compute durations

Option 5: introduce a TimePoint type, counted in TAI, that can convert from/to DateTime (probably in addition to option 2)

Option 6: like option 5, but make struct DateTime(TimePoint, Tz)

No problem! I tried to make the top-post as easy to digest as possible and requiring no context so it's possible to read it without knowledge of the past discussions...

Random thought: the information could also be written in `Cargo.toml`, and just stripped out of it by `cargo publish` before uploading to the repo? Not sure whether this idea holds...

Even better would be to use `crossbeam-utils`'s `Backoff`, I guess.

:+1: To explain the wasm-related changes: - task-local-extensions requires tokio with the rt feature, which does not support the wasm async runtime - reqwest does not support the timeout function...

Hey! Just checking if you had the time to have a look at my replies to your comments? :)

Makes sense, please let me know what your conclusions are about http::Extensions and task_local_extensions! As for testing on wasm in github CI, unfortunately wasm-timer only supports wasm32-unknown-unknown (with web_sys support)...

Arbitrary impls usually don't have anything more configurable by the user. Considering the `scale` issue, I think an `impl Arbitrary for BigDecimal { ... }` where the contents of the...