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
Compute tag_name a maximum of once per document owner #11318
Conversation
Thanks for the pull request, and welcome! The Servo team is excited to review your changes, and you should hear from @Manishearth (or someone else) soon. |
Heads up! This PR modifies the following files:
|
-S-awaiting-review +S-needs-code-changes Nice work, @mitchhentges.
|
d63d07a
to
4760443
Compare
New code was committed to pull request. |
4760443
to
67fb968
Compare
New code was committed to pull request. |
67fb968
to
93ac2c8
Compare
New code was committed to pull request. |
93ac2c8
to
d3a987f
Compare
New code was committed to pull request. |
@bors-servo try -S-awaiting-review @Ms2ger Do you know if there are tests for changing a element's owner document and checking its tag name?
|
Compute tag_name a maximum of once per document owner Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy --faster` does not report any errors - [X] These changes fix #1471 (github issue number if applicable). Either: - [X] These changes do not require tests because no new functionality was added, just a reorganization and caching of existing functionality Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/11318) <!-- Reviewable:end -->
💔 Test failed - linux-dev |
Unit tests are failing:
|
I'm sorry, but this is r- from me because of the unsafe code. |
/// owner changes. | ||
#[derive(JSTraceable)] | ||
struct TagName { | ||
ptr: UnsafeCell<Option<Atom>>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with @Ms2ger, why is this an UnsafeCell
rather than a Cell
or RefCell
?
84a8cd8
to
cc67a80
Compare
@bors-servo try I think this needs expectation changes, so |
Compute tag_name a maximum of once per document owner Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: - [x] `./mach build -d` does not report any errors - [X] `./mach test-tidy --faster` does not report any errors - [X] These changes fix #1471 (github issue number if applicable). Either: - [X] These changes do not require tests because no new functionality was added, just a reorganization and caching of existing functionality Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/11318) <!-- Reviewable:end -->
☀️ Test successful - android, arm32, arm64, linux-dev, linux-rel, mac-dev-unit, mac-rel-css, mac-rel-wpt, windows-dev |
Just these four expectation changes, right? |
No, we didn't implement the right thing before, so there should be new unexpected passing tests. The fact that there are none means new tests need to be written. |
Hold on, did this change behaviour? |
Mmmh guess I was wrong about that, sorry it has been a long time since I looked at that PR. :/ |
|
||
/// Retrieve a copy of the current inner value. If it is `None`, it is | ||
/// initialized with the result of `cb` first. | ||
#[allow(unsafe_code)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's remove the two #[allow(unsafe_code)]
attributes; should then be good to go.
cc67a80
to
1ca4a3e
Compare
18th time the charm 😉 |
@bors-servo r+ Thanks again for your contribution! |
📌 Commit 1ca4a3e has been approved by |
Compute tag_name a maximum of once per document owner Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: - [x] `./mach build -d` does not report any errors - [X] `./mach test-tidy --faster` does not report any errors - [X] These changes fix #1471 (github issue number if applicable). Either: - [X] These changes do not require tests because no new functionality was added, just a reorganization and caching of existing functionality Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/11318) <!-- Reviewable:end -->
☀️ Test successful - arm32, arm64, linux-dev, linux-rel, mac-dev-unit, mac-rel-css, mac-rel-wpt, windows-dev |
Thank you for contributing to Servo! Please replace each
[ ]
by[X]
when the step is complete, and replace__
with appropriate data:./mach build -d
does not report any errors./mach test-tidy --faster
does not report any errorsEither:
Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process.
This change is