Repository navigation
Documenting satisfying trait bounds and candidate preference #2070
Description
Activity
These all look like great things!
Just FYI, we are planning on moving the Generics chapter underneath the Types chapter. Additionally, we are planning to add "Generic Arguments" to the Generics chapter, which are currently mostly missing (but lightly touched on in the Paths chapter). I don't think that should disrupt you too much, but just so you are aware.
I'm trying to relate this list to how these items might fit in the existing structure. It could be helpful to show the outline in terms of how it fits in and the planned scope. So for example:
- Types
- Generics
- instantiating generic parameters of an item (new section)
- Alias types (new chapter)
- Trait and lifetime bounds
- satisfaction (new section)
- Generics
…etc.
And just to repeat what you said to make sure I understand: It can be challenging to split it into smaller pieces because there are cyclical dependencies like equality → normalization → satisfying trait bounds → equality. Is that right?
I understand it can be difficult to sketch out the whole picture before you start building. It's expected that as you start writing the shape will become more apparent to you, and things might need to shift around as you discover how to present it.
Whenever it's possible to split things into smaller PRs, that's preferable. I understand that isn't always easy. It's OK to leave placeholders to help break the work up into smaller pieces. For example, if you need to talk about "inference variables", but that by itself could be a meaty topic, then leaving a note that it is incomplete is fine (for example, see https://doc.rust-lang.org/1.90.0/reference/names/name-resolution.html where we needed to talk about name resolution, but haven't finished describing the actual process).
I think overall what you are proposing looks great!
- Types
My goal is to document the changes from #120752.
This requires a lot of interdependent concepts, so it's currently a fairly big change. How do you want me to proceed here? Concretely, I would like to get input on the general structure here before discussing the specifics of this doc.
The things in bold are what I am am adding/have to add to document things. What does this rely on:
Ways in which these things are interdependent:
Additional dependencies and annoyances:
I don't mind splitting this up into smaller changes and keeping things either as TODO or just not documenting things, e.g. we could just never explain what it means to "equate a type" until that gets merged separately or ignore satisfying trait bounds via item bounds of rigid aliases.
What I would like to know is:
A WIP branch is in https://github.com/rust-lang/project-goal-reference-expansion/pull/7/files. Started a zulip convo for this.