-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking issue for Rust high-pri or blocking issues for Servo & Gecko #2853
Comments
The fix for rust-lang/rust#15750 looks good! There are a few cases it still doesn't handle properly (see rust-lang/rust#16617) but I was able to work around all of those. |
No longer blocking on rust-lang/rust#16643; desugaring the for loop myself is a fine workaround for now. |
rust#14344 isn't fixed yet, but we appear to have found a workaround so it is not blocking anything. |
Today’s Rust upgrade is blocked on rust-lang/rust#18659 |
rust-lang/rust#18671 is no longer blocking. |
rust-lang/rust#19318 is killing me right now. |
Wouldn't rust-lang/cargo#1171 be worked-around by getting packages from crates.io instead of from git? |
@tshepang crates.io has a size limit on packages, 10 MB I believe. A Skia checkout (not counting the git repository) is ~45 MB. |
Wow, that package is very very not-small. Thanks for the info. |
The current Rust upgrade is blocked on one of rust-lang/rust#21883 or rust-lang/rust#21884 being fixed. (I’d prefer the latter. The former is just one instance of this problem, there might be other I haven’t found yet.) |
Chris and some others fixed the stability of hash and time, I added a check to ensure that doesn't happen again. It isn't perfect, but we can also bypass this using |
Gonk blocker: rust-lang/cargo#1293 |
Not a blocker (until next week), but rust-lang/cargo#1351 |
rust-lang/rust#23338 has a work-around, but happens a lot and gets tedious. |
html5ever is hitting rust-lang/rust#23407 |
rust-lang/rust#23488 prevents us from having good performance monitoring on linux |
html5ever keeps running into rust-lang/rust#23110 in the test suite. |
Servo's #2385 (compile-fail tests) is ever more of a concern as our plugins grow more magical. The upstream ticket is rust-lang/rust#12335. |
@kmcallister https://github.com/laumann/compiletest-rs exists and #5646 is tracking integrating it. |
Cool. |
Rust-in-Gecko blocker: rust-lang/rust#25342 (Alex/Felix are already aware of it) |
rust-lang/rust#25748 will block the next rustup (unless we find at least a work around). |
rust-lang/cargo#1897 blocks cargoup (#7049). |
rust-lang/rust#28559 blocks rustup |
|
I want to make changes (servo/rust-cssparser#90) that trigger rust-lang/rust#28934, and so would block our next rustup. |
rust-lang/libc#70 blocks #8446 (probably) |
As an update on the Cargo side of things, of the issues that're mentioned here:
|
Thanks for the update! Things look great overall. You're right that we can wait on the other two. Some clarifying comments below, but I don't have any pushback on punting them.
|
@larsbergstrom Regarding caching, I think part of the problem is a lack of clarity about the design constraints/requirements. At some point, we can more aggressively seek them out. But it's not obvious to me when the right timing is, or whether e.g. it's best to let Gecko try to find their own way first. (It's not clear whether a naive wrapping of Any sense on when this is likely to become a real issue? I would assume not until they're building a serious amount of Rust code? |
@aturon I'll ask around. I suspect that it depends on whether or not Rust/Cargo "behave well" with the new artifact builds in Firefox (https://groups.google.com/forum/#!topic/mozilla.dev.builds/jGg69m0x6Ck ). That is, can we just download all of the prebuilt files in the object dir and have things work? CC @ncalexan (who did much of that work). |
@larsbergstrom this ticket is pretty broad, and the discussion of caching doesn't really say what you want to do. Artifact builds download the major compiled libraries from Mozilla's automation; the big one is @rillian is the person I tap to keep abreast of Rust/Gecko integration progress -- perhaps he can add color here? |
@ncalexan Sorry about that! I'll move the convo out of the metabug off to where it should be (rust-lang/cargo#1997). |
Most of the Servo-critical stuff here has been fixed. Issues relevant to using Rust/Cargo in Gecko have been moved to an internal google doc. |
This issue will track all of the high-priority or blocking issues that Servo currently is waiting on in Rust. Issues created in Rust should reference this issue, and this top comment will be updated with links to those issues.
Rust
Bugs
Faster incremental builds
rust-lang/rust#27840
Optimized representations
rust-lang/rfcs#317
Cross memory-model data
rust-lang/rfcs#318
Virtual structs
jdm's requirements: https://gist.github.com/jdm/9900569
Leading current proposal: rust-lang/rfcs#349
Expose variadic functions to C
Right now, we work around it with a manual wrapper:
https://github.com/servo/servo/blob/master/ports/gonk/src/native_window_glue.cpp#L19-L22
Integer overflow
We'd love to at least have it per-crate, but honestly we'd consider shipping with it on by default.
rust-lang/cargo#2262
and: http://robert.ocallahan.org/2016/02/rewrite-everything-in-rust.html:
we should try to make Rust release builds check for integer overflow by default.
Cargo
Rustdoc
The text was updated successfully, but these errors were encountered: