ruby-dev (Japanese) list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: merch-redmine@jeremyevans.net
To: ruby-dev@ruby-lang.org
Subject: [ruby-dev:51090] [Ruby master Bug#18067] Composite procs with `instance_exec` aren't executed within the context of the receiver
Date: Mon, 09 Aug 2021 17:57:28 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-93197.20210809175727.12651@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-18067.20210808130917.12651@ruby-lang.org>

Issue #18067 has been updated by jeremyevans0 (Jeremy Evans).


I think this is expected.  You get the same error if you compose the proc manually, and the proc composition operators should reflect the same behavior as manual composition:

```ruby
func1 = -> (x) { x + y }

class A
  def y
    10
  end
end

A.new.instance_exec(1, &func1) # => 11

func2 = -> (x) { x * 2 }
f = ->(x) { func2.(func1.(x)) }
A.new.instance_exec(1, &f) # => undefined local variable or method `y' for main:Object (NameError)
```

----------------------------------------
Bug #18067: Composite procs with `instance_exec` aren't executed within the context of the receiver
https://bugs.ruby-lang.org/issues/18067#change-93197

* Author: ttanimichi (Tsukuru Tanimichi)
* Status: Open
* Priority: Normal
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN
----------------------------------------
```ruby
func1 = -> (x) { x + y }

class A
  def y
    10
  end
end

A.new.instance_exec(1, &func1) # => 11

func2 = -> (x) { x * 2 }
f = func1 >> func2
A.new.instance_exec(1, &f) # => undefined local variable or method `y' for main:Object (NameError)
```



-- 
https://bugs.ruby-lang.org/

      reply	other threads:[~2021-08-09 17:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-08 13:09 [ruby-dev:51088] " info
2021-08-09 17:57 ` merch-redmine [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-93197.20210809175727.12651@ruby-lang.org \
    --to=merch-redmine@jeremyevans.net \
    --cc=ruby-dev@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).