-
Notifications
You must be signed in to change notification settings - Fork 542
Leap approaches #1577
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
Leap approaches #1577
Conversation
@ErikSchierboom Leap approaches for Rust ready for review |
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.
Lovely content! I like the tables listing when something is evaluated
…nt.md Co-authored-by: Erik Schierboom <erik_schierboom@hotmail.com>
Co-authored-by: Erik Schierboom <erik_schierboom@hotmail.com>
@ErikSchierboom Nice suggestions about making the "cheat" comment a caution. I would think a caution would be more for warning how the code might be bad (e.g. cause an error), but in this case, using a "cheat" would be against the purpose of the exercise, so in a way it would be bad code. Will be ready for merge after the checks complete. Thanks again! |
Yeah it is meant for bad code, but in this case I think it might warrant repurposing it :) |
Initial commits for file structure and code. Details to follow...