rust-lang / rust-lang/reference

Conditional coercion sites, and materials on the subject of type inference algorithm.

Open
#1,124 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-coercions
Dominant language
Rust
Stars
1.6k
Forks
607
PR merge metrics
PR metrics pending

Description

Hello! We know that in the expression y = x, coercion may or may not happen, depending on whether y has explicit type annotation. So it seems this may be some form of "conditional coercion site" or something?

This seems to be highly related to the type inference algorithm, whose description is also seriously lacking.

Thanks!

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.

Research direction

No files or tests are identified. Start by surveying the Rust Reference sections covering coercion and type inference, then define the missing concepts, terminology, and scope before proposing documentation changes; done means the relevant behavior and inference relationship are clearly documented with appropriate examples.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.