Skip to content
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

Better explanation #3696

Closed

Conversation

postmeback
Copy link

Fixes: #3561

Copy link

@kenden kenden left a comment

Choose a reason for hiding this comment

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

In my humble opinion, this is a bit harder to read with this change.

Maybe the problematic phrase in bug #3561 could be simply changed to:

- Then we can create a vector to hold that enum and so, ultimately, holds different types. 
+ Then we can create a vector to hold that enum. So, in effect, that vector will hold different types. 

src/ch08-01-vectors.md Outdated Show resolved Hide resolved
Changes are per suggestion
src/ch08-01-vectors.md Outdated Show resolved Hide resolved
Extra spaces removed
@postmeback
Copy link
Author

If it serves the purpose, then would request to merge it. :)

@chriskrycho
Copy link
Contributor

Thank you for the PR! After reading the context, I decided #3874 was a better fix here, though, so I am closing this in favor of that. 👍🏼

@chriskrycho chriskrycho closed this Apr 1, 2024
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.

Bad phrasing
3 participants