> Le 6 oct. 2017 à 03:27, Nicholas Nethercote <n.netherc...@gmail.com> a écrit : > > 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.
I'm very strongly against moving more crates in servo/servo. Just publish the thing. _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
