Least-Upper-Bound coercions don't document special behaviour of coercing to fnptrs

Open Beginner friendly
#2,094 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
documentation

Research direction

Start in the Rust Reference section documenting type coercions and read the existing least-upper-bound coercion rules. Update the documentation to state how LUB coercions involving function items or closures fall back to function pointers when no mutual supertype exists, and ensure the provided example is covered by the explanation.

Written by the indexing model from the issue text.

Description

A-coercions 
fn foo() {}
fn bar() {}

let a = match true {
    true => foo,
    false => bar,
};

Here we wind up with a LUB coercion between two different function item types. This succeeds by coercing both types to function pointers.

The current documentation for type coercions defines LUB coercions as simply trying one-to-one coercion both ways and then trying to compute a mutual supertype if that fails. It should also document that when we have a LUB coercion between function item types and closures we'll coerce to a function pointer if there's no mutual supertype.

Dominant language
Rust
Stars
1.6k
Forks
607
Avg merge
1d 1h
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-lang/reference

All issues in rust-lang/reference

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.