-
Notifications
You must be signed in to change notification settings - Fork 58
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this 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 | | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice
Rendered