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

Fix isValue check for actor creation #102

Merged
merged 4 commits into from
Jan 30, 2017
Merged

Conversation

smarr
Copy link
Owner

@smarr smarr commented Jan 30, 2017

The isValue check for actor creation was broken. Instead of checking on the actual value the actor is created from, it is checking on the module or nil.
So, there was a huge isolation issue in the actor implementation.

This fixes #101.

@smarr smarr added the bug Fixes an issue, incorrect implementation label Jan 30, 2017
@smarr smarr force-pushed the check-isvalue-for-actor-creation branch from 0b4d577 to ac8753c Compare January 30, 2017 10:31
Signed-off-by: Stefan Marr <git@stefan-marr.de>
Signed-off-by: Stefan Marr <git@stefan-marr.de>
Add proper exception and remove todo.

Note, this change stops using the DSL for the IsValue node, because it was generating wrong code, and passing a `null` to isValue.execute*.

Signed-off-by: Stefan Marr <git@stefan-marr.de>
This is to ensure the actor classes are values.

Signed-off-by: Stefan Marr <git@stefan-marr.de>
@smarr smarr force-pushed the check-isvalue-for-actor-creation branch from ac8753c to c39b644 Compare January 30, 2017 10:45
@coveralls
Copy link

Coverage Status

Coverage increased (+0.01%) to 79.496% when pulling c39b644 on check-isvalue-for-actor-creation into e63a63a on master.

@smarr smarr merged commit 8ac11b5 into master Jan 30, 2017
@smarr smarr deleted the check-isvalue-for-actor-creation branch January 30, 2017 11:12
@smarr smarr added this to the v0.2.0 milestone Mar 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes an issue, incorrect implementation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants