Skip to content

Add link to Why Associated Type #2926

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

Merged
merged 1 commit into from
Feb 16, 2022
Merged

Add link to Why Associated Type #2926

merged 1 commit into from
Feb 16, 2022

Conversation

ifsheldon
Copy link
Contributor

Add link to Why Associated Type, which is my thought on the design of Associated Type. It's not about How, but Why, so I'd rather like to place it under Thoughts, not Walkthroughs.

@nellshamrell
Copy link
Contributor

@MATRIXKOO, @Folyd could you help me review this one?

@Folyd
Copy link
Contributor

Folyd commented Feb 16, 2022

Hi, @ifsheldon. Thanks for the PR. I strongly recommend you submit one PR of Rust Why after the book is finished instead of multiple PRs each with a single article.

@ifsheldon
Copy link
Contributor Author

ifsheldon commented Feb 16, 2022

I don't think that is gonna work. I still have multiple articles to write, some of which may not be submitted to TWiR. And a bundle of articles is just too long to read. The article is self-contained, so there's no context tightly related to the book/ article collection itself. The articles are just loosely gathered around a topic, which is a big WHY, so I would rather like people can jump right into the one WHY they're interested in without the need to scan through all other articles.

Copy link
Contributor

@nellshamrell nellshamrell left a comment

Choose a reason for hiding this comment

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

Ty!

@nellshamrell nellshamrell merged commit 0aff468 into rust-lang:master Feb 16, 2022
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.

3 participants