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

What is the difference between this fork and the original project? #11

Open
ghost opened this issue Jul 20, 2015 · 1 comment
Open

What is the difference between this fork and the original project? #11

ghost opened this issue Jul 20, 2015 · 1 comment

Comments

@ghost
Copy link

ghost commented Jul 20, 2015

I read your message indicating this is an upstream fork, but I was still not able to answer my question.

Regards 😄

@ghost
Copy link
Author

ghost commented Jul 21, 2015

Alright, I was able to gather that your fork

The go block which spawns a lightweight process always returns a channel that holds the final value from the process sleep was a special operation that you could yield, but if you wanted an actual channel that timed out you had to use timeout instead. I removed sleep so you always use timeout which makes it more consistent.
I added a takem instruction which stands for "take maybe". If an Error object is passed through the channel it will throw it automatically at the place were takem was yielded.

Are there any plans to merge back with origin? Also, are you still actively working on this? Last commit was quite a while ago.

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

No branches or pull requests

0 participants