Skip to content

/ servo

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

Jump to bottom

Use pipe::oneshot everywhere #121

Closed
brson opened this issue Oct 14, 2012 · 2 comments
Closed

Use pipe::oneshot everywhere #121

brson opened this issue Oct 14, 2012 · 2 comments
Labels
I-perf-bloat I-refactor

Comments

@brson
Copy link
Contributor

@brson brson commented Oct 14, 2012

Probably rename oneshot to something better too.

For message responses, these are more efficient than pipes::Chan. We should get in the habit of using them.
@brson
Copy link
Contributor Author

@brson brson commented Oct 14, 2012

I believe oneshot also enforces that the send happens too. So when used as a response channel provides something like guaranteed delivery (or failure).
@jdm
Copy link
Member

@jdm jdm commented Apr 18, 2014

Doesn't exist any longer.
@jdm jdm closed this Apr 18, 2014
ChrisParis pushed a commit to ChrisParis/servo that referenced this issue Sep 7, 2014
@dontcallmedom
Merge pull request servo#121 from w3c/license
3b5c4a7 
add a clear license for the TS
glennw added a commit to glennw/servo that referenced this issue Jan 16, 2017
@glennw
Merge pull request servo#121 from glennw/refactor-3
5af3880 
Refactoring in prep work for gpu clipping.
@jdm jdm mentioned this issue Nov 5, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
I-perf-bloat I-refactor
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@jdm @brson
You can’t perform that action at this time.