[#39810] 2.0 feature questionnaire — SASADA Koichi <ko1@...>
I made a questionnaire "What do you want to introduce in 2.0?" in my
2011/10/1 SASADA Koichi <[email protected]>:
Hi,
On Sun, Oct 2, 2011 at 1:30 AM, Yukihiro Matsumoto <[email protected]> wro=
Oops, I was mentioned.
See below.
(10/07/2011 02:19 PM), Evan Phoenix wrote:
>> No, it isn't. =A0MVM-aware extensions shall obey the MVM-safe APIs.
2011/10/1 SASADA Koichi <[email protected]>:
On Monday, October 24, 2011 at 10:29 PM, Charles Oliver Nutter wrote:
On Mon, Oct 24, 2011 at 10:29 PM, Charles Oliver Nutter <[email protected]
On Tue, Oct 25, 2011 at 3:51 PM, Rocky Bernstein <[email protected]> wrote:
On Tue, Oct 25, 2011 at 1:51 PM, Rocky Bernstein <[email protected]>wrote:
[#39823] Discussion results — SASADA Koichi <ko1@...>
Hi,
I did not have the fortune of attending the discussion, but I would
Hi,
Hello Matz,
Hello,
On Mon, Oct 3, 2011 at 8:16 AM, Yusuke Endoh <[email protected]> wrote:
How does String#margin behave when given irregular input?
On Mon, Oct 3, 2011 at 11:05 AM, Jim Freeze <[email protected]> wrote:
Sent from my iPad
On Mon, Oct 3, 2011 at 1:52 PM, Gmail <[email protected]> wrote:
On Mon, Oct 3, 2011 at 14:16, Yusuke Endoh <[email protected]> wrote:
[#39824] Road to 2.0 — SASADA Koichi <ko1@...>
Hi,
Hello,
[#39886] [Ruby 1.9 - Bug #5393][Open] some style fixes in enum.c docs — b t <redmine@...>
[#39888] [Ruby 1.9 - Feature #5394][Open] Anonymous Symbols, Anonymous Methods — Kurt Stephens <ks.ruby@...>
[#39915] [Ruby 1.9 - Feature #5400][Open] Remove flip-flops in 2.0 — Magnus Holm <judofyr@...>
Hello,
[#39918] [Ruby 1.9 - Bug #5401][Open] Ruby 1.9.3 interpreter crash — Conrad Taylor <conradwt@...>
[#39937] redmine 2.0 tracker — SASADA Koichi <ko1@...>
There is no 2.0 tracker (sub-project) in redmine.
[#39957] [Ruby 1.9 - Bug #5407][Open] Cannot build ruby-1.9.3-rc1 with TDM-GCC 4.6.1 on Windows XP SP3 — Heesob Park <phasis@...>
[#39986] problems with Refinements — Shugo Maeda <shugo@...>
Hi,
There are also the group of people that think refinements are just a
Hi,
> Unfortunately, I missed Brian's talk, so we have to wait until the
Hi,
> I am not sure why
[#39993] [Ruby 1.9 - Feature #2348] RBTree Should be Added to the Standard Library — David Graham <david.malcom.graham@...>
(2011.10.07 01:50 ), David Graham wrote:
On 07/10/2011, at 1:16 PM, Kenta Murata wrote:
(2011/10/07 1:50), David Graham wrote:
On Thu, Oct 6, 2011 at 6:34 PM, SASADA Koichi <[email protected]> wrote:
[#40058] Statistical Profiling — Perry Smith <pedzsan@...>
Would it be plausible to somehow, get the (ruby) stack of the running =
[#40073] [Ruby 1.9 - Feature #5427][Open] Not complex patch to improve `require` time (load.c) — Yura Sokolov <funny.falcon@...>
[#40117] [Ruby 1.9 - Bug #5437][Open] Using fibers leads to huge memory leak — Robert Pankowecki <robert.pankowecki@...>
[#40172] plans for 2.0. — Carter Cheng <cartercheng@...>
Hello,
2011/10/17 Carter Cheng <[email protected]>:
[#40188] [Ruby 2.0 - Feature #5454] keyword arguments — Yukihiro Matsumoto <matz@...>
This looks very interesting=21 Would someone be willing to translate to e=
Hi,
Hi,
Thanks for the translation=21
RnJvbSB0aGUgY3VycmVudCBwYXRjaCBpdCBzZWVtcyB0byBtZSB0aGF0IHRoaXMgd291bGQgcmFp
[#40200] [Ruby 1.9 - Bug #5459][Open] Silence -Wmissing-declarations and -Wold-style-definition warnings in mkmf — Nikolai Weibull <now@...>
[#40203] invoking garbage_collect in gc.c — Carter Cheng <cartercheng@...>
Hello,
[#40259] Counseling — Perry Smith <pedzsan@...>
Ruby and I are back in counseling... Its always the same thing with =
What's your $LC_CTYPE? What OS are you on?
Hi all,
Gon軋lo Silva wrote:
On Oct 21, 2011, at 9:43 AM, Perry Smith wrote:
To try and cut to the core of the issue: in Ruby 1.8 it was common practi=
> What Ruby needs (IMHO), is the equivalent of Obj-C's NSData class. That is,
On Saturday, October 22, 2011 at 12:43 PM, Jon wrote:
[#40271] Can rubygems save us from "binary-compatibility hell"? — Yusuke Endoh <mame@...>
Hello, rubygems developers --
Forwarding this again to ruby-core as received a postmaster delivery failur=
Hello,
On Thu, Nov 10, 2011 at 4:38 PM, Yusuke Endoh <[email protected]> wrote:
Hello,
2011/11/10 Yusuke Endoh <[email protected]>:
Hello,
Dne 22.10.2011 4:48, Yusuke Endoh napsal(a):
On Oct 31, 2011, at 2:41 PM, V=EDt Ondruch wrote:
Dne 1.11.2011 0:05, Eric Hodel napsal(a):
On Nov 1, 2011, at 2:03 PM, V=EDt Ondruch wrote:
[#40281] [Ruby 2.0 - Bug #5470][Open] r33507 and r33508 break the build under MinGW — Luis Lavena <luislavena@...>
[#40284] set_trace_func changed? — Intransition <transfire@...>
Did something change about `set_trace_func` between 1.8.7 and 1.9.3?
[#40290] [ruby-trunk - Feature #5474][Assigned] keyword argument — Yusuke Endoh <mame@...>
Hi,
Hi,
See below.
Hi,
> |> It's Python way, and I won't take it.
More refinement below. I think we're on a good path here.
Hi,
On Wed, Oct 26, 2011 at 2:08 PM, Yukihiro Matsumoto <[email protected]>wrote:
Hi,
On Wed, Oct 26, 2011 at 7:30 PM, Yukihiro Matsumoto <[email protected]> wr=
Hi,
On Thu, Oct 27, 2011 at 3:16 AM, Nobuyoshi Nakada <[email protected]> wrot=
Hi,
[#40311] [ruby-trunk - Feature #5478][Open] import Set into core, add syntax — Konstantin Haase <Konstantin.Haase@...>
On 2011-12-04, at 16:15:00, Alexey Muranov wrote:
[#40312] [ruby-trunk - Feature #5479][Open] import StringIO into core, add String#to_io — Konstantin Haase <Konstantin.Haase@...>
On Tue, Oct 25, 2011 at 10:14:54PM +0900, Charles Nutter wrote:
My main request was to add String#to_io, as Aaron described, so this protoc=
On Wed, Oct 26, 2011 at 02:22:21AM +0900, Haase, Konstantin wrote:
[#40314] [ANN] 2011 Call for grant proposals — Shugo Maeda <shugo@...>
Hello,
Hello,
> Ruby reference manual for you, me and everyoneApplicant: Yutaka Hara
[#40316] [ruby-trunk - Feature #5481][Open] Gemifying Ruby standard library — Hiroshi Nakamura <nakahiro@...>
On Tue, Oct 25, 2011 at 14:45, Intransition <[email protected]> wrote:
[#40322] [ruby-trunk - Feature #5482][Open] Rubinius as basis for Ruby 2.0 — Thomas Sawyer <transfire@...>
Come back when all 1.9 features and callcc are implemented :-)
(2011/10/25 12:46), Yusuke Endoh wrote:
On Mon, Oct 24, 2011 at 9:58 PM, SASADA Koichi <[email protected]> wrote:
On Tue, Oct 25, 2011 at 11:45 PM, Tim Felgentreff <[email protected]> wrote:
[#40356] JIT development for MRI — Carter Cheng <cartercheng@...>
Hello,
Hello Charlie,
Hi,
Dear Koichi SASADA,
I noticed that you used context threading in YARV. Do you have some analysis
Thanks for reference.
Thanks Koichi.
On Wed, Oct 26, 2011 at 6:43 PM, Carter Cheng <[email protected]> wrote:
Hi Carter,
Thanks Koichi. How do profiling based approaches differ from trace recording
[#40412] [ruby-trunk - Bug #5486][Open] rb_stat() doesn’t respect input encoding — Nikolai Weibull <now@...>
On Fri, Oct 28, 2011 at 07:28, Usaku NAKAMURA <[email protected]> wrote=
On Fri, Oct 28, 2011 at 08:14, Nikolai Weibull <[email protected]> wrote:
On Sun, Mar 11, 2012 at 22:41, Nobuyoshi Nakada <[email protected]> wrote:
Hello,
2012/3/15 U.Nakamura <[email protected]>:
[#40427] cfp consistency error — Aaron Patterson <tenderlove@...>
Hi, I'm getting a cfp consistency error when I use trunk ruby. Here is
[#40453] Test case format — Jon <jon.forums@...>
I see no mention of a required (or preferred) test case format after reviewing:
2011/10/27 Jon <[email protected]>:
[#40489] [ruby-trunk - Bug #5497][Open] Math.log10(10_000) error on HP-UX/PA — The Written Word Inc <bugs-ruby@...>
[#40492] [ruby-trunk - Feature #5505][Open] BasicObject#__extend__ — Thomas Sawyer <transfire@...>
[#40527] [ANN] Ruby 1.9.3-p0 is out — "Yuki Sonoda (Yugui)" <yugui@...>
-----BEGIN PGP SIGNED MESSAGE-----
Hello,
On Sun, Oct 30, 2011 at 11:11 PM, Luis Lavena <[email protected]> wrote:
On Sun, Oct 30, 2011 at 11:20 AM, Yugui <[email protected]> wrote:
> On Sun, Oct 30, 2011 at 11:20 AM, Yugui <[email protected]> wrote:
[#40562] [ruby-trunk - Bug #5525][Open] UDPSocket#bind(ip, port) fails under IPv6 => Errno::EAFNOSUPPORT — Iñaki Baz Castillo <ibc@...>
[#40571] [ruby-trunk - Bug #5529][Open] Bus error with Fibers on OSX Lion — Dave Thomas <dave@...>
[#40586] [ruby-trunk - Feature #5531][Open] deep_value for dealing with nested hashes — Kyle Peyton <kylepeyton@...>
[ruby-core:39922] Re: [Ruby 1.9 - Feature #5372][Open] Promote blank? to a core protocol
On 03/10/11 22:25, Eric Hodel wrote:
> On Oct 2, 2011, at 2:38 PM, Alex Young wrote:
>> Eric Hodel wrote in post #1024462:
>>> On Sep 27, 2011, at 6:52 PM, Alex Young wrote:
>>> Can you show me a description of the opposite?
>>
>> What I mean by "in reverse" is that with the Null Object, we have an
>> instance which silently does the right thing. We don't have to care that
>> it's null, we just call methods on it like we would on a non-Null
>> instance.
>>
>> With a #null? or #blank? method, we instead have a way to ask each
>> instance directly whether it's null, without having to care about its
>> class. If it quacks like a null, then it's null.
>
> I mean, on the C2 wiki or somewhere else on the internet. Can you show other languages that have benefited from a similar implementation? If there is such a document maybe it can help us understand.
To my knowledge it's most similar to Either in Haskell, but you have to
squint a bit to see it:
http://haskell.org/ghc/docs/6.12.2/html/libraries/base-4.2.0.1/Data-Either.html
If you renamed #empty? to #left? the similarity should be a little clearer.
If you look at Perl 6, there's also a stack of similar-looking
functionality around Mu, Failure and Whatever - specifically the
.defined method is close to what I'm thinking, but they've taken it a
*lot* further.
>
>>>> Because the core API commonly returns nil in error cases..
>>>
>>> Can you show some examples? I don't seem to write nil checks very often
>>> when using core methods, but maybe I am forgetting.
>>
>> Having a quick look over the core docs, there's quite a few in
>> File::Stat and Process::Status, all the try_convert() methods,
>> Kernel.caller, Kernel.system, arguably String#slice and Regexp#match
>> (although I can't see the latter being reasonably alterable), and
>> Thread#status at least.
>
> When does caller return a non-Array?
$ irb
ruby-1.9.2-p290 :001 > caller(22)
=> nil
It's when the depth parameter exceeds the current stack depth.
>
>>>> case thingy
>>>> when Blank
>>>> # catch-all
>>>> # other cases
>>>> end
>>>
>>> What about:
>>>
>>> case thingy
>>> # other cases
>>> else
>>> # catch-all
>>> end
>>
>> Yep, that's another way to do the same sort of thing, but with a Blank
>> or Null it's more explicit and more flexible. With a bare
>> "case...else..." you have to handle both correct nulls and erroneous
>> values in the "else" clause. With Null, you can leave the "else" clause
>> purely for handling the error case, where you've somehow got a response
>> you weren't expecting. I think it's clearer.
>
> The problem I see is that adding #empty? to every class is confusing.
Part of that is down to the name. #null? is better because it doesn't
imply that the receiver is a container.
You'll notice that I *didn't* suggest an implementation for Symbol:
sometimes it doesn't make sense for any instance of a class to be null.
You could make the same argument about Numeric, but I've occasionally
found treating #zero? as a null test to be useful in the past.
>
> Should File::Stat#empty? returning true to mean the file is empty? Or should it always return false to say "the file exists"
I'd go for the latter, personally.
> What would Process::Status#empty? mean? Would false mean that the program had exited non-zero or that the program had exited with any status?
I mentioned upthread that it would be useful aliased to #exited?, but
I'd really prefer it to test whether the process was actually running -
from the documentation of #exited? it sounds like processes that
segfault will cause #exited? to return false.
>
> Kernel#system and Thread#status return true, false, or nil, so combining "non-zero exit" and "command failed" into #empty? isn't clearer to read than 'if system(command) then else abort "#{command} failed" end'
Sure. I'd say Kernel#system is an interesting example, though. Say I
was being implementing it as a third-party library, but with a twist:
instead of returning nil on command failure, I want to capture some
details about the failure and wrap them up in a hypothetical
ProcessFailure instance. Some of the time, I don't care about the
details of the failure, and other times I do, but in no case do I think
of this as warranting an Exception. Now, if I say:
class ProcessFailure
def null?
true
end
end
then when I *don't* care which happened, either the command failing or
it having a non-zero exit, I can just say:
unless mysystem(foo).null?
# it worked!
end
and when I *do* care, it's:
unless (result = mysystem(foo)).null?
# it worked!
else
# It didn't, so try to do something useful with the error details
$stderr.puts result.to_s if result
end
Note that while it might make the conditionals cleaner here, I *can't*
do the obvious thing of:
class ProcessFailure < FalseClass; end
because that's just not how booleans work.
> While it might make String#split or Regexp#match and try_convert usage clearer, it adds much confusion otherwise.
As I mentioned above, there are definitely cases where null? should
never be true for a given class because if you have a value, it's not
null by definition. It's simple enough to leave the default #null? ->
false implementation in place for them.
--
Alex