Project

General

Profile

Actions

Feature #17407

closed

Fiber.current and require 'fiber'

Added by zverok (Victor Shepelev) over 3 years ago. Updated about 3 years ago.

Status:
Closed
Assignee:
-
Target version:
-
[ruby-core:101529]

Description

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,

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.

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0