[#51329] [ruby-trunk - Feature #7677][Open] YAML load mode that does instantiate Ruby — "trans (Thomas Sawyer)" <transfire@...>
7 messages
2013/01/09
[#51347] [ruby-trunk - Bug #7679][Open] IRB history is broken — "zzak (Zachary Scott)" <zachary@...>
15 messages
2013/01/10
[#51348] [ruby-trunk - Bug #7680][Open] IRB autocompletion doesn't autocomplete methods — "zzak (Zachary Scott)" <zachary@...>
8 messages
2013/01/10
[#51389] [ruby-trunk - Bug #7688][Open] Error hiding with rb_rescue() on Comparable#==, #coerce and others — "Eregon (Benoit Daloze)" <redmine@...>
34 messages
2013/01/11
[#59674] [ruby-trunk - Feature #7688] Error hiding with rb_rescue() on Comparable#==, #coerce and others
— "marcandre (Marc-Andre Lafortune)" <ruby-core@...>
2014/01/09
[#59675] [ruby-trunk - Feature #7688] Error hiding with rb_rescue() on Comparable#==, #coerce and others
— "marcandre (Marc-Andre Lafortune)" <ruby-core@...>
2014/01/09
[#59679] Re: [ruby-trunk - Feature #7688] Error hiding with rb_rescue() on Comparable#==, #coerce and others
— "Martin J. Dürst" <duerst@...>
2014/01/10
On 2014/01/10 7:42, marcandre (Marc-Andre Lafortune) wrote:
[#51391] [ANN] Implementer Meeting — Aaron Patterson <tenderlove@...>
Hey everyone,
9 messages
2013/01/11
[#51421] Re: [ANN] Implementer Meeting
— Mark Rada <markrada26@...>
2013/01/14
Hello Aaron,
[#51431] Re: [ANN] Implementer Meeting
— Marc-Andre Lafortune <ruby-core-mailing-list@...>
2013/01/14
I'm worried about issues with Enumerator::Lazy. Should we discuss this at
[#51399] [ruby-trunk - Bug #7689][Open] Crash @enumerator.so with ruby 1.9.3/thin/RoR 3.2.11 — "saepia (Marcin Lewandowski)" <marcin@...>
6 messages
2013/01/12
[#51441] [ruby-trunk - Bug #7699][Open] rubyspec failed: BigDecimal#divmod Can be reversed with * and + — "mrkn (Kenta Murata)" <muraken@...>
8 messages
2013/01/15
[#51453] [REMINDER] Implemeter Meeting — Aaron Patterson <tenderlove@...>
Hey everyone,
5 messages
2013/01/15
[#51454] [CommonRuby - Feature #7701][Open] Non-optional (required) keyword args — "headius (Charles Nutter)" <headius@...>
31 messages
2013/01/15
[#53256] [CommonRuby - Feature #7701] Non-optional (required) keyword args
— "headius (Charles Nutter)" <headius@...>
2013/03/09
[#51496] Ruby 2.0 Meeting Schedule — Aaron Patterson <tenderlove@...>
At the Implemeters Meeting, we talked about meeting again in 2 weeks
5 messages
2013/01/17
[#51497] Schedule next developer meeting — Aaron Patterson <tenderlove@...>
At the last meeting, we agreed upon having another meeting four weeks
5 messages
2013/01/17
[#51499] [ruby-trunk - Feature #7712][Open] Add .txt extensions to all plain-text documentation files for Windows users — "postmodern (Hal Brodigan)" <postmodern.mod3@...>
9 messages
2013/01/18
[#51545] Haiku port problem — Paulo Geyer <paulogeyer@...>
I'm trying to port ruby 1.9.3-p347 to Haiku (http://www.haiku-os.org/)
5 messages
2013/01/21
[#51578] [ruby-trunk - Bug #7729][Open] __dir__ returns a absolute dir path — "authorNari (Narihiro Nakamura)" <authorNari@...>
8 messages
2013/01/23
[#51623] [ruby-trunk - Feature #7739][Open] Define Hash#| as Hash#reverse_merge in Rails — "alexeymuranov (Alexey Muranov)" <redmine@...>
24 messages
2013/01/24
[#51726] [ruby-trunk - Feature #7751][Open] How to encapsulate File.delete and File.rename into one 'transaction'? — "mghomn (Justin Peal)" <yujianbin@...>
5 messages
2013/01/29
[#51735] [ruby-trunk - Bug #7752][Open] Rational/Float/Fixnum/Bignum `.to_s.encoding` is US-ASCII — "coffeejunk (Maximilian Haack)" <mxhaack@...>
6 messages
2013/01/29
[ruby-core:51506] Re: [ruby-trunk - Bug #7702][Open] Remove Proc#binding
From:
Rocky Bernstein <rockyb@...>
Date:
2013-01-18 07:11:05 UTC
List:
ruby-core #51506
I suspect it would have a negative impact on the ability to write a debugger. I seem to recall noting (I think it was from the pry person) that the equivalent of ruby-debug's binding_n was impossible in 2.0 and perhaps a patch was added to include it back. However, given the gap between what is desirable in writing a good debugger and where things have been going in MRI, my current view is that there should be two separate interpreters. In this way, the concerns of good debugging don't have to run up against the concerns of good security or performance. And so far, the trend has been that debuggers have been losing. What can be done in 1.9 with respect to debugging is not as good comprehensive as what was available in 1.8. And in 2.0, I am not certain things will change that much although it appears that things will be different. On the other hand, with respect to the two interpreter approach I also do believe that one should be able debug optimized code -- even if that means putting more burden on the programmer to understand more of the transformations, optimizations or run-time behavior of the interpreter. While one might not guarantee that Proc#binding is available because some kind of optimization took place, I think it a mistake to remove it in those cases where it could have been provided by using the same mechanisms that were in place previously. On Tue, Jan 15, 2013 at 7:09 PM, jballanc (Joshua Ballanco) < [email protected]> wrote: > > Issue #7702 has been reported by jballanc (Joshua Ballanco). > > ---------------------------------------- > Bug #7702: Remove Proc#binding > https://bugs.ruby-lang.org/issues/7702 > > Author: jballanc (Joshua Ballanco) > Status: Open > Priority: Normal > Assignee: > Category: > Target version: > ruby -v: 2.0.0-preview1 > > > =begin > As discussed in the most recent Ruby implementer's meeting and elsewhere > over the years, being able to get a handle to the binding of any block/proc > has a number of problems: > > * Code execution after passing a block/proc in unpredictable, as the > binding of said proc can be used to redefine any local, instance variable, > method, class, module, etc. > * Potentially sensitive data can leak out of the scope of a method via a > proc binding > * Large object graphs may need to be retained for the lifetime of a proc, > since any identifier in scope at the time of proc creation must remain live > in the event that the binding of the proc is used to evaluate code > > Additionally, removal of Proc#binding would enable a number of very useful > optimizations and performance improvements. > =end > > > > -- > http://bugs.ruby-lang.org/ > >