Skip to content

Conversation

@milibopp
Copy link
Contributor

@milibopp milibopp commented Nov 4, 2014

The introduction of object-safety for coercion to trait objects (see rust-lang/rfcs#255) affects the previous implementation of BoxIter. It turns out trait objects are not actually necessary to deal with this situation, so
the implementation was changed to be generic over the type of iterator instead of the type iterated over.

The introduction of object-safety for coercion to trait objects (see
rust-lang/rfcs#255) affects the previous implementation of BoxIter. It turns
out trait objects are not actually necessary to deal with this situation, so
the implementation was changed to be generic over the type of iterator instead
of the type iterated over.
@bluss
Copy link
Member

bluss commented Nov 12, 2014

The point of it is to wrap a Box<Iterator>, and if that is no longer possible this struct needs to be removed.

@milibopp
Copy link
Contributor Author

I see… ok, I simply wanted to make the crate compile again, so I didn't notice I was undermining this struct's entire purpose in doing so. There may be another way though, I haven't looked at this in very much detail.

@bluss
Copy link
Member

bluss commented Nov 14, 2014

Fair enough. I've removed the struct for now. Thanks anyway.

@bluss bluss closed this Nov 14, 2014
@milibopp milibopp deleted the box_iter_without_trait_objects branch November 17, 2014 13:11
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.

2 participants