Make sure all type checking rules are covered.

Open
#595 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by examining the type-checking rules implemented in the librustc_typeck crate and comparing them with the Rust Reference. Identify which rules are absent from the Reference and document them; done means the relevant type-checking rules are covered.

Written by the indexing model from the issue text.

Description

A-types

librustc_typeck is a rather large crate that does a lot of things. Presumably there are a lot of rules in there that are not covered in the reference.

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.