[#100689] [Ruby master Feature#17303] Make webrick to bundled gems or remove from stdlib — hsbt@...
Issue #17303 has been reported by hsbt (Hiroshi SHIBATA).
11 messages
2020/11/02
[#100852] [Ruby master Feature#17326] Add Kernel#must! to the standard library — zimmerman.jake@...
Issue #17326 has been reported by jez (Jake Zimmerman).
24 messages
2020/11/14
[#100930] [Ruby master Feature#17333] Enumerable#many? — masafumi.o1988@...
Issue #17333 has been reported by okuramasafumi (Masafumi OKURA).
10 messages
2020/11/18
[#101071] [Ruby master Feature#17342] Hash#fetch_set — hunter_spawn@...
Issue #17342 has been reported by MaxLap (Maxime Lapointe).
26 messages
2020/11/25
[ruby-core:100925] [Ruby master Feature#17331] Let Fiber#raise work with transferring fibers
From:
nicholas.evans@...
Date:
2020-11-18 00:50:16 UTC
List:
ruby-core #100925
Issue #17331 has been reported by nevans (Nicholas Evans). ---------------------------------------- Feature #17331: Let Fiber#raise work with transferring fibers https://bugs.ruby-lang.org/issues/17331 * Author: nevans (Nicholas Evans) * Status: Open * Priority: Normal ---------------------------------------- This seems like a feature that would be just as useful for transferring fibers as it is for yielding fibers. I'm using a kwarg, so this is not automatic; the caller must know how to handle the fiber. If you call a yielding fiber with `transfer: true` or a transferring fiber without `transfer: true`, a `FiberError` will be raised. ```ruby yielding_fiber.raise "message" transferring_fiber.raise "message", transfer: true ``` Implementation: https://github.com/ruby/ruby/pull/3783 -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>