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

Move get_buffer_requests into rust-layers from Servo #94

Merged
merged 1 commit into from Jul 31, 2014

Conversation

@mrobinson
Copy link
Member

mrobinson commented Jul 30, 2014

This is generally useful and layers now know how to get their own
BufferRequests.


self.get_buffer_requests_for_layer(root_layer.clone(),
requests,
window_rect_in_device_pixels);

This comment has been minimized.

@zwarich

zwarich Jul 30, 2014

Contributor

It seems like the nesting here wouldn't be too bad if this were just a plain match, rather a match with an early return defining a local.

This comment has been minimized.

@mrobinson

mrobinson Jul 30, 2014

Author Member

I had to do this do avoid a double borrow actually. Rust complained that I borrowed self twice, once for self.root and once for self.get_buffer_requests_for_layer.

@mrobinson
Copy link
Member Author

mrobinson commented Jul 30, 2014

I found a bug in this pull requests, but I will update it soon with a fixed version.

This is generally useful and layers now know how to get their own
BufferRequests.
@mrobinson
Copy link
Member Author

mrobinson commented Jul 31, 2014

Okay. I've fixed the bug in the previous version of the PR. Things seem to be working well now.

zwarich pushed a commit that referenced this pull request Jul 31, 2014
Move get_buffer_requests into rust-layers from Servo
@zwarich zwarich merged commit ea2fb4a into servo:master Jul 31, 2014
@mrobinson mrobinson deleted the mrobinson:more-cleanup branch Sep 8, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

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