Skip to content

Conversation

@graydon
Copy link
Contributor

@graydon graydon commented Nov 23, 2012

Nothing too substantial, just tidying stuff up that erickt found.

r? @erickt or @brson perhaps?

@brson
Copy link
Contributor

brson commented Nov 23, 2012

Why remove get_ref?

@nikomatsakis
Copy link
Contributor

I would definitely keep get_ref() and lose with(). In general, I think that the with() pattern is better written using lifetimes and immutable pointers. In this case, we have to rely on some unsafe code to get it to type check, but the interface is safe.

@graydon
Copy link
Contributor Author

graydon commented Dec 3, 2012

The removal of get_ref grew out of trying to make #4020 work, but as I commented in that bug I think the idea of a "resettable future" is itself nonsensical and should be reformed to use pipe::oneshot. I'll update this to leave get_ref in and remove with and, I think, close the other one. Agreed?

@graydon
Copy link
Contributor Author

graydon commented Dec 11, 2012

landed in a55ea48

@graydon graydon closed this Dec 11, 2012
RalfJung added a commit to RalfJung/rust that referenced this pull request Nov 21, 2024
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.

3 participants