Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upIntroduce a new type MaybeUnreflectedDom<T> (fixes #25701) #25781
Conversation
highfive
commented
Feb 17, 2020
|
Heads up! This PR modifies the following files:
|
highfive
commented
Feb 17, 2020
|
@bors-servo try=wpt |
|
|
|
All the failures are either the solid white intermittent issue or a silent crash that happens sometimes. |
|
That silent crash doesn't even reproduce locally. |
|
Could you give me an overview of what this PR is doing? It's not clear to me how all the pieces fit together to fix #25701. |
Sure. What it does is that it roots the boxed not-yet-reflected DOM instance with a different smart pointer type than |
|
This is a nice solution to the problem! Thanks for explaining it to me. |
|
@bors-servo r+ |
|
|
|
|
|
Not sure if this crash is my fault or not, we'll see how the other build jobs fare. |
|
This is getting us pretty close to being able to support lazy creation of DOM reflectors. |
|
This only works because the |
|
Hmm, so we'd need support for dynamic dispatch of trace methods if we want to support subtyping of maybe-reflected DOM objects. |
|
Tried to reproduce the issue locally and failed. @bors-servo retry |
|
|
|
@bors-servo retry |
|
|
nox commentedFeb 17, 2020
No description provided.