[#101179] Spectre Mitigations — Amel <amel.smajic@...>
Hi there!
5 messages
2020/12/01
[#101180] Re: Spectre Mitigations
— Chris Seaton <chris@...>
2020/12/01
I wouldn’t recommend using Ruby to run in-process untrusted code in the first place. Are people doing that?
[#101694] Ruby 3.0.0 Released — "NARUSE, Yui" <naruse@...>
We are pleased to announce the release of Ruby 3.0.0. From 2015 we
4 messages
2020/12/25
[ruby-core:101529] [Ruby master Misc#17407] Fiber.current and require 'fiber'
From:
zverok.offline@...
Date:
2020-12-18 23:08:44 UTC
List:
ruby-core #101529
Issue #17407 has been reported by zverok (Victor Shepelev). ---------------------------------------- Misc #17407: Fiber.current and require 'fiber' https://bugs.ruby-lang.org/issues/17407 * Author: zverok (Victor Shepelev) * Status: Open * Priority: Normal ---------------------------------------- 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](https://docs.ruby-lang.org/en/2.0.0/Fiber.html#method-c-current), * the actual code is defined in the core [cont.c](https://github.com/ruby/ruby/blob/master/cont.c#L2480) * the `ext/fiber.c` [does very little](https://github.com/ruby/ruby/blob/master/ext/fiber/fiber.c) 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. -- 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>