Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix weird spec failure caused by magic matcher: has_error => be_error
- Loading branch information
1 parent
d2ac3ad
commit 528a99a
Showing
2 changed files
with
8 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
528a99a
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With EM 0.12.1 (released Real Soon Now), you can nest EM.run without having to check EM::reactor_running? explicitly.
528a99a
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, there’s one remaining problem with that design though.
EM::run {} blocks the first time, and is async in future calls. This can have important semantic meaning.
Any which way, EM::run {} needs to be as high in the stack as possible. I’d love to see it moved to a loader in it’s entirety.