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

Improve the correctness of Root lifetimes #3493

Merged
merged 1 commit into from Sep 27, 2014
Merged

Improve the correctness of Root lifetimes #3493

merged 1 commit into from Sep 27, 2014

Conversation

zwarich
Copy link

@zwarich zwarich commented Sep 26, 2014

Use the new lifetime bounds feature of Rust to enforce that the
RootCollection field of Root outlives the jsref field. This still
doesn't enforce that the Root itself outlives the jsref field, and
doing this would require some sort of init dance.

Use the new lifetime bounds feature of Rust to enforce that the
RootCollection field of Root outlives the jsref field. This still
doesn't enforce that the Root itself outlives the jsref field, and
doing this would require some sort of init dance.
@hoppipolla-critic-bot
Copy link

Critic review: https://critic.hoppipolla.co.uk/r/2703

This is an external review system which you may optionally use for the code review of your pull request.

In order to help critic track your changes, please do not make in-place history rewrites (e.g. via git rebase -i or git commit --amend) when updating this pull request.

@zwarich
Copy link
Author

zwarich commented Sep 26, 2014

r? @jdm

bors-servo pushed a commit that referenced this pull request Sep 26, 2014
Improve the correctness of Root lifetimes

Reviewed-by: jdm
bors-servo pushed a commit that referenced this pull request Sep 27, 2014
Improve the correctness of Root lifetimes

Reviewed-by: jdm
@bors-servo bors-servo merged commit 78f061e into servo:master Sep 27, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants