-
Notifications
You must be signed in to change notification settings - Fork 544
Changes to Xorcism discussed in #1040 #1041
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
Conversation
It's going to be at least another day until I can review this properly--we're well into New Year's Eve now, in my time zone at least--but I can say that the failing CI is because you edited
That should sort out the CI failure. |
Thank you for the pointer! I'll try to get CI fixed. And no pressure at all from me, have a great New Year's. |
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.
Looks good! One nit remains that I'd like to see fixed before merging, but overall, I'm happy with this PR.
I have reviewed all changes made up to this point, and confirmed that it addresses all points raised in #1040. I have not yet run this locally to verify that bonus tests still pass (IIRC, our CI doesn't yet know how to handle those), but I see no reason why they wouldn't.
OK, the build is fixed. Let me know if you'd like me to rebase at this point. |
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.
Thanks for working on this! I have now verified locally that all tests, including feature tests, pass.
Awesome, thank you! I really appreciate all of the work you and the team put into the exercises here. It was invaluable when I was learning Rust, and has been a huge asset in my teaching. |
This should implement all of the changes discussed in #1040, barring one. Outside of a comment around
impl Trait
and removing the link toExactSizeIterator
, I did not modify the instructions in README.md. I believe with the change in tests to focus onmunge_in_place
first, the user will have sufficient ramp-up experience implementing the simpler exercise before jumping into the more complex one.