Skip to content

sub-trait coercions #18600

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
nrc opened this issue Nov 4, 2014 · 5 comments
Closed

sub-trait coercions #18600

nrc opened this issue Nov 4, 2014 · 5 comments
Labels
A-DSTs Area: Dynamically-sized types (DSTs) C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC

Comments

@nrc
Copy link
Member

nrc commented Nov 4, 2014

Where trait T: U { ... } , implictly coerce from &T to &U, etc.

See RFC 401.

Part of #18469

@steveklabnik
Copy link
Member

another #18469

@steveklabnik steveklabnik added the A-DSTs Area: Dynamically-sized types (DSTs) label Jan 27, 2015
@frewsxcv
Copy link
Member

What's the status of this?

@isabelmu
Copy link
Contributor

isabelmu commented Oct 9, 2016

I think this is a duplicate of #5665 (although that bug was filed before RFC 401 was adopted).

@Mark-Simulacrum Mark-Simulacrum added the C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC label Jul 22, 2017
@Mark-Simulacrum
Copy link
Member

Going to go ahead and close in favor of #5665.

@crlf0710
Copy link
Member

Current tracking issue for this is #65991

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A-DSTs Area: Dynamically-sized types (DSTs) C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC
Projects
None yet
Development

No branches or pull requests

6 participants