Move FastTransform to webrender_api crate#4883
Conversation
Signed-off-by: Nico Burns <nico@nicoburns.com>
|
It's not a small patch, so I would like to know what @mrobinson thinks about this making future webrender syncs harder or such. Maybe it should land upstream, and then sync? Seems it has been a while. |
|
Ah, I had though the |
|
I've sent this upstream as https://bugzilla.mozilla.org/show_bug.cgi?id=2046918. Maybe we can try and include it in the upcoming sync if it lands soon. |
|
I think the current state (without this PR) may actually be causing a relatively significant slowdown in clean build times for Servo, because it seems to be serializing the build of WebRender (including it's build script) and |
|
We will likely re-sync and re-release soon due to servo/servo#45728, so if you can land this upstream it should be included in the next release. |
|
I will try to land upstream soon. Will have to work out why it got rejected by CI last time (I'm currently having trouble with Mozilla try access) |
servo-malloc-size-ofandservo-geometryare currently depending onwebrenderbecause they need theFastTransformtype. As these crates are low in the crate graph, this means that ~50 servo crates need to recompile when modifying webrender.This PR, moves
FastTransformintowebrender_apiwhich means thatservo-malloc-size-ofandservo-geometrycan also depend only onwebrender_apiand the only servo crates that needs to depend onwebrenderareservo-paintandservo.Servo PR: servo/servo#45485