Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Avoid leaky backref captures in procs #8726

@headius

Description

@headius

CRuby appears to have started to address the leaky frames of procs when used for regular expression matching. They seem to be doing this to better support writing intermediate functions in Ruby, but the effect is the same: a proc's captured frame variables don't leak back into the original frame.

At least two PRs related to this:

ruby/ruby#7225

ruby/ruby#7282

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions