-
Notifications
You must be signed in to change notification settings - Fork 5
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
Q: Why fibers? #24
Comments
/cc @grosser |
fibers was the only way I found to make
if you find any other way, please make a PR, I'd like to avoid fibers too :) |
Interesting, thanks. When I go back in the commit history, I see a version that didn't use fibers I think. It's not clear to me what in that version wouldn't have worked with those factors, but maybe I'll find some time to play around with it and find out for myself. Thanks for pointing out the requirements that you ran into trouble with -- are those requirements pretty well captured by tests, so if I find an implementation that passes the tests, it's got a pretty good chance of meeting the requirements that you found fibers necessary to meet? |
Also I hadn't realized this gem, in addition to supplying |
The tests are pretty extensive, so if you get them green your good to go :) I'll add some docs to the readme. On Sat, Nov 8, 2014 at 8:18 AM, Jonathan Rochkind notifications@github.com
|
@grosser Thanks for explaining. We should document it in the README. @jrochkind In master I've took over most cucumber around scenarios from RSpec. Feel free to play with the implementation :) PRs are very welcome! Due to vacation my response time remains slow until next week 🌞 |
@jrochkind I don't know if you are still fighting One option is to simply use For more complete and nicer minitest hooks you might have a look at @jeremyevans' minitest-hooks! |
As Please note that Closing. |
Not an issue, just wondering if you could share just a few words on why the current version of minitest-around uses Fibers, what motivated that choice?
I am greatly missing
around
from Minitest/spec, and am considering this gem, but want to understand what it's doing and why first to make sure I understand what I'm getting into. It's not obvious to me the benefit of using Fibers there instead of a simpler implementation (like in older versions of this gem?).Thanks for any information!
The text was updated successfully, but these errors were encountered: