Possible future dependency cycle?

The following seem to form a cycle or will in the future

  • ahash 0.6 depends on getrandom
  • getrandom 0.2 optionally depends on wasm-bindgen
  • wasm-bindgen 0.2.69 optionally depends on serde_json
  • serde_json optionally depends on indexmap
  • indexmap depends on hashbrown 0.9
  • hashbrown in git depends on ahash 0.6.

It is unlikely to happen in practice but can cargo handle the case where all the optional features are enabled?

Currently, that seems to mean that a future version of hashbrown (say, 0.10) will indirectly depend on hashbrown 0.9. This doesn't seem to be a problem.

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.