Skip to content

Lang/libs coordination question: okay for libs to stabilize traits with final fn in them? #160394

Description

@joshtriplett

Filing this issue to get a definitive answer on whether @rust-lang/lang has any concerns about @rust-lang/libs-api stabilizing APIs in the standard library that use final fn.

If we stabilize such an API, that commits us to keeping this mechanism. That seems fine to me, as we have an accepted RFC and we seem to have a consistent expectation of shipping/stabilizing final fn.

Tracking issue for final fn: #131179

Metadata

Metadata

Assignees

No one assigned

    Labels

    I-lang-nominatedNominated for discussion during a lang team meeting.I-lang-radarItems that are on lang's radar and will need eventual work or consideration.P-lang-drag-1Lang team prioritization drag level 1. https://rust-lang.zulipchat.com/#narrow/channel/410516-t-langS-waiting-on-t-langStatus: Awaiting decision from T-langT-langRelevant to the language teamT-libsRelevant to the library team, which will review and decide on the PR/issue.T-typesRelevant to the types team, which will review and decide on the PR/issue.disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions