Skip to content

Add type system docs 2025h2 goal #314

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

BoxyUwU
Copy link
Member

@BoxyUwU BoxyUwU commented Jun 17, 2025

Copy link
Contributor

@nikomatsakis nikomatsakis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks pretty good. Left two follow-up questions.


| Task | Owner(s) or team(s) | Notes |
|------------------------------|---------------------|-------|
| Triage Analysis Chapter | @BoxyUwU | |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| Triage Analysis Chapter | @BoxyUwU | |
| Discussion and Moral Support | [Types] | |
| Triage Analysis Chapter | @BoxyUwU | |


### The next 6 months

- Compile a list of type system concepts then compare that against the in-compiler documentation and the rustc-dev-guide's type system chapter to find weak points in our documentation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this be made available somewhere? Either posted on the types team repo? o perhaps a tracking issue? or open up (best) individual tracking issues? I think we should do that.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would expect to put a summarized list in the project goal tracking issue, and then also have associated issues in the dev guide repo tracking each individual topic/area 🤔 Having stuff in the types repo may make sense too though

- Compile a list of type system concepts then compare that against the in-compiler documentation and the rustc-dev-guide's type system chapter to find weak points in our documentation.
- Document existing known weak points:
- How const generic arguments are type checked
- The design of the new solver and how/why it differs from the old solver
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants