Skip to content

sub-trait coercions #18600

Closed
Closed
@nrc

Description

@nrc
Member

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

See RFC 401.

Part of #18469

Activity

steveklabnik

steveklabnik commented on Jan 27, 2015

@steveklabnik
Member

another #18469

frewsxcv

frewsxcv commented on Nov 18, 2015

@frewsxcv
Member

What's the status of this?

isabelmu

isabelmu commented on Oct 9, 2016

@isabelmu
Contributor

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

added
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
on Jul 22, 2017
Mark-Simulacrum

Mark-Simulacrum commented on Jul 22, 2017

@Mark-Simulacrum
Member

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

crlf0710

crlf0710 commented on Aug 16, 2021

@crlf0710
Member

Current tracking issue for this is #65991

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-DSTsArea: Dynamically-sized types (DSTs)C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @steveklabnik@frewsxcv@crlf0710@nrc@Mark-Simulacrum

        Issue actions

          sub-trait coercions · Issue #18600 · rust-lang/rust