Ruby Issue Tracking System

05/21/2021

02:36 PM Ruby master Bug #17875: Segfault when reusing a closed Fiber scheduler inside a Thread

Oh, thanks! I installed 3.1.0-dev and it worked fine for me, too. (That is, it failed with a nice error message and b... rmosolgo (Robert Mosolgo)

05/20/2021

08:46 PM Ruby master Bug #17875: Segfault when reusing a closed Fiber scheduler inside a Thread

Ah, yes, thanks for linking back to that. It sure looks like the same thing. I searched for "fiber scheduler segfault... rmosolgo (Robert Mosolgo)

08:12 PM Ruby master Bug #17875 (Closed): Segfault when reusing a closed Fiber scheduler inside a Thread

Hi! I've been trying to learn the new `Fiber.scheduler` API. I ran into this segfault when I was misusing scheduler i... rmosolgo (Robert Mosolgo)

06/12/2018

02:16 PM Ruby master Feature #14844 (Open): Future of RubyVM::AST?

Hi! Thanks for all your great work on the Ruby language.
I saw the new RubyVM::AST module in 2.6.0-preview2 and I... rmosolgo (Robert Mosolgo)

02/28/2017

12:35 PM Ruby master Feature #12901: Anonymous functions without scope lookup overhead

I didn't think about (er, *know* about!) those ways of accessing the inner scope. That definitely rules out skipping ... rmosolgo (Robert Mosolgo)

02:09 AM Ruby master Feature #12901: Anonymous functions without scope lookup overhead

What about checking at the block level? I mean, could we check that:
- All local variable reads come from the bloc... rmosolgo (Robert Mosolgo)

01/20/2017

02:11 PM Ruby master Feature #13125: MRI has too much Qtrue : Qfalse;

> "reverse" of RTEST()
How about ...
- CTEST()
- TEST2BOOL()
- C2BOOL()
Hope those help brainstorm a bi... rmosolgo (Robert Mosolgo)

11/22/2016

10:21 PM Ruby master Feature #12901: Anonymous functions without scope lookup overhead

ko1 mentioned a similar possibility in his RubyConf talk about Guilds. An "isolated proc" would be a good option to p... rmosolgo (Robert Mosolgo)

11/04/2016

06:01 PM Ruby master Feature #12901: Anonymous functions without scope lookup overhead

Much +1 for this feature, I used anonymous functions extensively in graphql-ruby until I learned about this overhead.... rmosolgo (Robert Mosolgo)