Marcel Laverdet
Marcel Laverdet
Thank you!
@vlasky See discussion here - https://github.com/laverdet/node-fibers/commit/8f2809869cc92c28c92880c4a38317ae3dbe654d
The fact is that the JS ecosystem as a whole has overwhelmingly chosen async/await over fibers. There may still be a niche community for fibers but my opinion is that...
@opyh this error message comes directly from v8 -- https://github.com/v8/v8/commit/e937bc5ed6b80851e8b0471dbc41d1ee4990d29a v8 sees fibers as archived threads, there's frankly no way around it. You will need to track down someone on...
> So I guess the short answer is, I shouldn't be letting a fiber that I care about get GCed. And in fact, the strategy of using `try { Fiber.yield...
If the fiber isn't accessible on the heap then that means there is no way of the fiber ever waking up, because you can't ever call `run` on it again....
I must warn you that your fix here replaces an error with a memory leak.
The `Future` library provides adapters to convert between JS-style promises and Fiber-style futures. An example of this: ```js const Future = require('fibers/future'); let task = Future.task(function() { let promise =...
@jedwards1211 yeah duh :). I made fibers in 2011 because it was painfully obvious that the tools we had were no good. We didn't get generators in nodejs until September...
GPL doesn't affect "software as a service" which I'd guess is the vast majority of nodejs usage. I'm allowed to distribute my source as MIT and use a GPL library...