On Fri, Oct 6, 2017, at 12:27 PM, Nicholas Nethercote wrote: > I see two options. > > - Overwrite the heapsize crate on crates.io with the malloc_size_of code. > So > the crate name wouldn't change, but the API would change significantly, > and > it would still be on crates.io. Then switch Servo over to using > heapsize > everywhere. > > - Switch Servo over to using malloc_size_of everywhere. (This leaves open > the > question of what should happen to the heapsize crate.) > > I personally prefer the second option, mostly because I view all of this > code > as basically unstable -- much like the allocator APIs in Rust itself -- > and > publishing it on crates.io makes me uneasy. Also, keeping the code in the > tree > makes it easier to modify. > > Thoughts?
There are multiple Servo dependencies on crates.io depend on heapsize. [1] How are they handled at the moment? And what would we do to them in the future with the second option? [1] https://crates.io/crates/heapsize/reverse_dependencies - Xidorn _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
