Skip to content

Resolve how to handle coercions and the like under default binding modes #44848

Closed
@nikomatsakis

Description

@nikomatsakis

One of the tricky questions that came up when implementing default binding modes is how to handle the compiler's current logic around patterns with ref bindings. Currently, if a ref-binding is included, this disables coercion for let statements and tweaks how we handle match statements. It's unclear precisely what we ought to do now that ref bindings are not always syntactically visible. This issue exists to track the question.

There has already been a number of conversations on the topic. Here are some links for background reading:

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-feature-requestCategory: A feature request, i.e: not implemented / a PR.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions