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

Unmapping after execution, extra tests and the GuardedSignalCommandMap #14

Merged
4 commits merged into from
Mar 13, 2011

Conversation

Stray
Copy link
Contributor

@Stray Stray commented Mar 13, 2011

Happy to split the Guarded map off into a separate repo, but the underlying changes in SCM are needed anyway.

Let me know if you want to keep it as 2 separate projects (I was going to but Neil Manuell had already done his work in a pull from this fork).

I guess we need to inform other forks of the potential problem?

Stray

Stray added 4 commits March 13, 2011 17:27
… behaviour ambiguities).

Tests to SignalCommandMap intended to clarify the injector behaviour when a value has not been dispatched by this signal but has been dispatched by a previous signal.
… the command is executed. GuardedSignalCommandMap completed - all tests passing.
@joelhooks
Copy link
Owner

Is it even possible to notify all the forks?

I make no warranty!

@Stray
Copy link
Contributor Author

Stray commented Mar 13, 2011

True :) Buyer-beware-stocks-may-go-down-as-well-as-up yada yada.

I'll blog it as well - it's interesting fodder about how tricky it is to trap corner cases as well. Always useful but difficult to test what your code doesn't do as well as what it does. The 'doesn't' being one of those autistic-people-can't-think-about-it questions. Like... what I didn't have for breakfast. A hippopotamus... and then the list is endless.

This pull request was closed.
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