facebook
Next steps?
As of this writing, to my knowledge, Regenerator is essentially feature-complete, and (with #170 now closed) all the bugs that I know about have been fixed. I know I'm going to be eating those words soon, but I feel good about everything right now!
What's next?
On the feature side, I would still like to improve source maps (#18) and support generator functions that are also async functions (#163).
On the code quality side, the test suite has good code coverage (91% according to #147) but it could be closer to 100%, and it would be great to have Coveralls running as part of the test suite.
I also hope to spend time examining generated code with an eye toward simplification. Dead code elimination, redundant assignments to context.next and context.prev, case labels that will never be jumped to, etc. Some of these inefficiencies can be avoided by the code generator, but other opportunities will probably have to be identified in a post-processing pass.
I know this codebase can be difficult to dive into, so I welcome contributions of any kind.
cc @amasad @termi @AnSavvides @mathiasbynens @Raynos @scttnlsn @agchou @jonathanong @spicyj @eventualbuddha @chenglou @jamesgpearce @xaka @cpojer @fkling @sciolist @RichardLitt @monsanto @maxnordlund @bartekn @radford @sebmck @bolinfest @rwaldron @ForbesLindesay
Ugh, I just remembered I forgot to report this one upstream. Perhaps relevant to the simplification discussion. https://github.com/babel/babel/issues/590
One thing that comes to mind is to be able to compile async/await to just generators and promises to be used in environments that have native support for generators like io.js
Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.
