Sinotov Aleksandr

> What's the advantage of using `serde_test` over `serde_json`? I know it has `test` in its name, so it _should_ be somehow more appropriate, but I feel like we are...

As workaround, we can use `HashMap::into_values` directly. ```rust let map: AHashMap = AHashMap::from_iter([("a", 1), ("b", 2)]); let arr = HashMap::into_values(map.into()).collect::(); println!("{:?}", arr); ```

> Sorry for taking so long to get back to you. I reinstalled everything with a newer toolchain, and recompiled cargo-instruments and it worked this time - so I assume...

Greetings! @hawkw Any update on this? Faced with same problem and implementing own Json-Layer is super counterproductive.

`std::string_view` from C++17?

Also, some symbols are not encoding, for example `#` and `@`.

> Either way, this feels less ergonomic than `tokio-postgres`. I don't share your view that using `let (res1, res2) = join!(q1, q2);` is too implicit. Imho, when I used `tokio-postgress`...

> You have the same field declared twice (I don't even know if serde is supposed to handle this), and you're not even giving a field named "path" to your...

> It's much simpler to just do: It's not an option for my case, because I have struct with generic. > you should take a look at [figment](https://docs.rs/figment/latest/figment/), another deserialization...

> Why you try to flatten fields that are effectively `Box` (because of `flatten`)? Sorry, what? I'm flattening `struct First` and `struct Second` which (as @edgarogh already said https://github.com/serde-rs/serde/issues/2261#issuecomment-1231980639) comes...