Feature #17407: Fiber.current and require 'fiber'

• Status: Closed
• Assignee: -
• Target version: -

[zverok (Victor Shepelev)]

Maybe it is not the right time to ask, but why one need to do require 'fiber' before using Fiber.current?

For what I can see,

• it is this way since their introduction,
• the actual code is defined in the core cont.c
• the ext/fiber.c does very little

I was just bitten by it again preparing the changelog (stuck with NoMethodError and for a few minutes thought the build is broken), is there a reason to have it this way?..
Just clarifying for docs sake, at least.

[Eregon (Benoit Daloze)]

Maybe we should just include these Fiber methods in core, and require 'fiber' would be a no-op (for compatibility)?
Agreed it's confusing such a core class has only half the documented methods defined without an extra require.

[nobu (Nobuyoshi Nakada)]

• Tracker changed from Misc to Feature

[nobu (Nobuyoshi Nakada)]

https://github.com/nobu/ruby/tree/fiber-builtin

[ko1 (Koichi Sasada)]

I still think Fiber.current is not needed because Fiber#transfer is not easy feature to use.
However, Fiber scheduler is introduced and they can be utilize.

So I'm okay for nobu's PR.

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed

Applied in changeset git|521ad9a13aef1e1dae4eaff70d3e6b2e358aa095.

---

Moved Fiber methods into core [Feature #17407]