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

Make sure that every code snippet has a comment that specifies the file path #382

Closed
phil-opp opened this issue Jan 2, 2018 · 1 comment
Labels
enhancement Potential improvements for the code or the blog. good first issue This is a good issue for a first contribution. Feel free to ask if you need help! help wanted We could use help for this issue/pull request!

Comments

@phil-opp
Copy link
Owner

phil-opp commented Jan 2, 2018

See this comment by sieken on the blog:

[…] I am a complete beginner in Rust, and follow this guide mainly to get a better grasp on operating system "basics". Your tutorials have been very good at explaining the code snippets in a simple manner, but sometimes it gets a bit confusing as to where functions and other code snippets should be placed in the file tree.. If you find the time, could you write the path/filename of where each code snippet goes? I'm sure it would be very helpful to other people who, like me, are not yet intuitive about "what parts go where".

I'm going to add this to the “Second Edition” milestone, but this would be also useful for the first edition, if anyone wants to do it.

@phil-opp phil-opp added enhancement Potential improvements for the code or the blog. good first issue This is a good issue for a first contribution. Feel free to ask if you need help! help wanted We could use help for this issue/pull request! labels Jan 2, 2018
@phil-opp phil-opp added this to the Second Edition milestone Jan 2, 2018
@phil-opp
Copy link
Owner Author

I think this is done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Potential improvements for the code or the blog. good first issue This is a good issue for a first contribution. Feel free to ask if you need help! help wanted We could use help for this issue/pull request!
Projects
None yet
Development

No branches or pull requests

1 participant