Skip to content

New Agent implementation. #412

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

Merged
merged 1 commit into from
Aug 29, 2015
Merged

New Agent implementation. #412

merged 1 commit into from
Aug 29, 2015

Conversation

jdantonio
Copy link
Member

Needs yardoc, but functionally complete.

@jdantonio jdantonio added the enhancement Adding features, adding tests, improving documentation. label Aug 28, 2015
@jdantonio jdantonio self-assigned this Aug 28, 2015
@jdantonio jdantonio added this to the 1.0.0 Release milestone Aug 28, 2015
@pitr-ch
Copy link
Member

pitr-ch commented Aug 28, 2015

Does it integrate with TVar as well?

@jdantonio
Copy link
Member Author

It does not integrate with TVar. That will be documented in the Yardoc. There is also a small bug with the "await" functions where there are nested actions. I will fix that today. fixed

@jdantonio jdantonio force-pushed the new-agent branch 3 times, most recently from 10487e0 to e68c0ae Compare August 29, 2015 09:15
jdantonio added a commit that referenced this pull request Aug 29, 2015
@jdantonio jdantonio merged commit 09a0eff into master Aug 29, 2015
@jdantonio jdantonio deleted the new-agent branch August 29, 2015 16:59
# ({#await}, {#await_for}, {#await_for!}, and {#wait}) from within an action
# block/proc/lambda. The call will block the Agent and will always fail.
# Calling either {#await} or {#wait} (with a timeout of `nil`) will
# hopelessly deadlock the Agent with no possibility of recovery.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we raise instead?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably. Interestingly, this is exactly the same as Clojure. I was surprised that Clojure took this approach but it is documented behavior.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, I would not have expected that in clojure. I would raise if it can be already detected (to protect our users) otherwise let's keep it as is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adding features, adding tests, improving documentation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants