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 upRemove Rc<T> usage from Range #8091
Conversation
|
|
|
Reviewed 1 of 1 files at r1, 1 of 1 files at r2. components/script/dom/range.rs, line 123 [r1] (raw file): Comments from the review on Reviewable.io |
|
@eefriedman is reviewing this PR. |
|
Review status: all files reviewed at latest revision, 1 unresolved discussion, all commit checks successful. components/script/dom/range.rs, line 123 [r1] (raw file): Comments from the review on Reviewable.io |
|
Review status: all files reviewed at latest revision, 1 unresolved discussion, all commit checks successful. components/script/dom/range.rs, line 123 [r1] (raw file): Comments from the review on Reviewable.io |
|
Review status: all files reviewed at latest revision, 1 unresolved discussion, all commit checks successful. components/script/dom/range.rs, line 123 [r1] (raw file): Comments from the review on Reviewable.io |
|
Review status: 0 of 1 files reviewed at latest revision, 1 unresolved discussion, some commit checks pending. components/script/dom/range.rs, line 123 [r1] (raw file): Comments from the review on Reviewable.io |
|
Reviewed 1 of 1 files at r3. components/script/dom/range.rs, line 124 [r3] (raw file): Comments from the review on Reviewable.io |
I initially used this to correctly handle ranges when their respective containers are mutated, to get weak references of Range objects. I now realise that the weak references should be handled at a lower-level, closer to the JS-managed object.
|
Review status: 0 of 1 files reviewed at latest revision, 1 unresolved discussion, some commit checks pending. components/script/dom/range.rs, line 124 [r3] (raw file): Comments from the review on Reviewable.io |
|
OK. r=me. |
|
@bors-servo r=eefriedman Thanks for the review! |
|
|
Remove Rc<T> usage from Range I initially used this to correctly handle ranges when their respective containers are mutated, to get weak references of Range objects. I now realise that the weak references should be handled at a lower level, closer to the JS-managed object. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8091) <!-- Reviewable:end -->
|
|
nox commentedOct 20, 2015
I initially used this to correctly handle ranges when their respective containers
are mutated, to get weak references of Range objects. I now realise that the weak
references should be handled at a lower level, closer to the JS-managed object.