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

Added some documentation on coroutines #53

Merged
merged 1 commit into from
Jul 28, 2015

Conversation

Hodapp87
Copy link
Contributor

I was trying to understand the coroutine code in order to make some additions to it, and in the process had added some of my own documentation. I think it's all correct, but it's my own guesswork.

@Hodapp87
Copy link
Contributor Author

@jameysharp you're welcome. What you've told me should help me fix things up a bit further. The commit message is indeed a mess - I rebased over a large range of commits, so I'll try to clean that up.

I'm a little new to GitHub pull request workflow - should I squash again and do a force push?

@jameysharp
Copy link
Contributor

A pull request is pretty unusual as git workflows go. It's the only case I can think of where a force push is a good idea. So yes, you can either squash again or git commit --amend, then force push. Thanks!

This is a combination of my own notes when trying to understand the coroutine
implementation, and an integration of the corrections and better explanations that
jameysharp provided.
@Hodapp87
Copy link
Contributor Author

Okay, I think I've integrated in everything that you noted (I'm checking your notes again now), and hopefully understood the details properly this time.

jameysharp added a commit that referenced this pull request Jul 28, 2015
Add documentation on coroutines: thanks, @Hodapp87!
@jameysharp jameysharp merged commit 7ecea58 into GaloisInc:master Jul 28, 2015
@Hodapp87 Hodapp87 deleted the coroutine_docs branch July 28, 2015 18:38
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.

2 participants