Define "concrete"

Open
#548 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
45/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
rust
Domain
documentation

Research direction

Search the Reference for the existing uses of “concrete”, then read the generics page and glossary structure. Define the term on the generics page, link each use and the glossary entry to it, and add examples of concrete and non-concrete types. Done means the definition, links, glossary entry, and examples are present and consistent.

Written by the indexing model from the issue text.

Description

New Content

We use it twice (soon to be thrice) but don't define it anywhere. It should be defined on the generics page as an item where all generic parameters have been instantiated with a non-generic type. The uses of "concrete" should link to this definition, and it should also be added to the glossary, again linking to the full definition.

We should also have examples that show that scalar types are concrete, types that don't have any generics are concrete, things like Option<u8> are concrete, and probably some counterexamples as well.

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.