1. 14
  1.  

  2. 2
    libyasna-080c400d17ab0fbc.rlib
    libyasna-38f10d7bdca324e3.rlib
    libyasna-3bbd36df87de5542.rlib
    libyasna-4ee5bbdf3224f90b.rlib
    libyasna-53051573765968ab.rlib
    libyasna-5a757cdb54d25cfc.rlib
    

    I wonder how much or Rust’s slow build times can be attributed to such dependency bloat? It would have been an interesting experiment if Cargo could force only a single “variant” of every dependency per build (it would also have been interesting to know how many builds would not have been able to “negotiate” such a constraint). Also would have opened the door to shared libraries…

    1. 4

      cargo hakari implements automation for “the workspace hack,” a trick in Rust to ensure that, at least when you’re working in a workspace of your own crates with some common shared dependencies, those dependencies are always compiled with the same feature set to avoid duplication.