Skip to content
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

Call BoxTreeRoot::construct from layout_thread_2020 #24360

Merged
merged 2 commits into from Oct 5, 2019
Merged

Conversation

@nox
Copy link
Member

nox commented Oct 3, 2019

This change is Reviewable

@nox nox requested a review from SimonSapin Oct 3, 2019
@highfive
Copy link

highfive commented Oct 3, 2019

warning Warning warning

  • These commits modify unsafe code. Please review it carefully!
unsafe impl Send for ServoLayoutNode<'_> {}
unsafe impl Sync for ServoLayoutNode<'_> {}
Comment on lines +111 to +117

This comment has been minimized.

Copy link
@SimonSapin

SimonSapin Oct 3, 2019

Member

I there a comment we could add here about the soundness of these impls?

This comment has been minimized.

Copy link
@nox

nox Oct 4, 2019

Author Member

I added a comment.

@@ -17,7 +17,7 @@ use style::properties::ComputedValues;
use style::selector_parser::PseudoElement;

#[derive(Clone, Copy)]
pub(super) enum WhichPseudoElement {
pub enum WhichPseudoElement {

This comment has been minimized.

Copy link
@SimonSapin

SimonSapin Oct 3, 2019

Member

Are all of these newly-pub items used in another crate? I wonder if could move the crate boundaries somehow to make the API surface smaller. Maybe add some wrapper structs with private fields, for things that are exposed?

This comment has been minimized.

Copy link
@nox

nox Oct 4, 2019

Author Member

The trait NodeExt needs to be public, and thus any item exposed by the trait needs to be public too, so WhichPseudoElement, among other types, needs to be public. I could wrap LayoutBox into a struct but I'm not sure that it is that useful to do so.

@nox nox force-pushed the build-box-tree branch from b244daa to ec74204 Oct 4, 2019
@SimonSapin
Copy link
Member

SimonSapin commented Oct 4, 2019

@bors-servo
Copy link
Contributor

bors-servo commented Oct 4, 2019

📌 Commit 1bb85ed has been approved by SimonSapin

@bors-servo
Copy link
Contributor

bors-servo commented Oct 5, 2019

Testing commit 1bb85ed with merge 36f70f5...

bors-servo added a commit that referenced this pull request Oct 5, 2019
Call BoxTreeRoot::construct from layout_thread_2020

<!-- Reviewable:start -->
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/24360)
<!-- Reviewable:end -->
@bors-servo
Copy link
Contributor

bors-servo commented Oct 5, 2019

☀️ Test successful - linux-rel-css, linux-rel-wpt, status-taskcluster
Approved by: SimonSapin
Pushing 36f70f5 to master...

@bors-servo bors-servo merged commit 1bb85ed into master Oct 5, 2019
2 of 3 checks passed
2 of 3 checks passed
continuous-integration/appveyor/pr AppVeyor build failed
Details
Taskcluster (pull_request) TaskGroup: success
Details
homu Test successful
Details
@bors-servo bors-servo deleted the build-box-tree branch Oct 5, 2019
@SimonSapin SimonSapin added this to Done / resolved in Layout 2020 Dec 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Layout 2020
  
Merged / resolved
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants
You can’t perform that action at this time.