Skip to content

Conversation

@KaustubhOG
Copy link

Closes #2303

This PR updates the outdated comment in the owned_mutation test
within exercises/19_smart_pointers/cow1.rs to better explain how
to_mut() behaves when the data is already owned.

@KaustubhOG
Copy link
Author

Hi!
This PR addresses #2303 by clarifying the comment in the owned_mutation test.
All checks have passed and there are no merge conflicts.
Please review when convenient — happy to make any adjustments if needed.
Thanks!

@KaustubhOG
Copy link
Author

Hi!

All checks have passed, there are no merge conflicts, and the PR fully addresses the linked issue.
Whenever you have a moment, @rust-lang/rustlings-maintainers, could you please review this?

Happy to make any updates or adjustments if needed. Thanks for your time and work on Rustlings! 🙌

@mo8it
Copy link
Contributor

mo8it commented Nov 17, 2025

I don't think that the new description is much better. Please stop annoying maintainers by pinging them repeatedly.

@mo8it mo8it closed this Nov 17, 2025
@KaustubhOG
Copy link
Author

Thanks for the feedback — and I’m truly sorry for the repeated pings.
I didn’t mean to add pressure, and I appreciate the clarification.
I’m still new to open-source and learning the etiquette.

It won’t happen again. Thanks for your time.

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.

[19_smart_pointers/cow1.rs] Stale comment in owned_mutation test is confusing

2 participants