DashMap uses private serde module

[thomcc]

If I attempt cargo install tokei, when building dashmap it fails with this error:

error[E0603]: module `export` is private
   --> /Users/thom/.cargo/registry/src/github.com-1ecc6299db9ec823/dashmap-3.11.10/src/serde.rs:5:12
    |
5   | use serde::export::PhantomData;
    |            ^^^^^^ private module
    |
note: the module `export` is defined here
   --> /Users/thom/.cargo/registry/src/github.com-1ecc6299db9ec823/serde-1.0.119/src/lib.rs:275:5
    |
275 | use self::__private as export;
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^

error[E0282]: type annotations needed
  --> /Users/thom/.cargo/registry/src/github.com-1ecc6299db9ec823/dashmap-3.11.10/src/serde.rs:58:38
   |
58 |         deserializer.deserialize_map(DashMapVisitor::<K, V>::new())
   |                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^ cannot infer type for type parameter `K`

error: aborting due to 2 previous errors

This is presumably the case for anything else using dashmap, at least with serde support.

The issue seems to be https://github.com/xacrimon/dashmap/blob/master/src/serde.rs#L5 which imports from a private module. You should instead use core::marker::PhantomData which is the same.

Ideally, you could fix this and also backport the fix to 3.x, e.g. cut a new patch release of 3.11.11 that contains just this minor fix, which will fix everything that is still depending on dashmap v3. (Obviously, you should also fix it for 4.x)

[thomcc]

This change happened in the most recent version of serde, e.g. in this commit serde-rs/serde@dd1f4b4

[ryzhyk]

Serde 1.0.119 broke semantic versioning by removing some std re-exports. I ran into the same issue with my project. Unfortunately, they wouldn't fix it: serde-rs/serde#1946

[thomcc]

I think serde's stance is reasonable, although I'd assume stuff like this can happen due to cargo fix suggestions and/or r-a autoimport, so I'd probably be a bit more sympathetic.

Either way, it needs to be fixed downstream in crates like this one.

[nvzqz]

@xacrimon can you please also release 3.11.11 with this fix, so that downstream crates aren't required to update to 4.x (for 4.0.2)?

[doivosevic]

any update on this?