[#53893] [ruby-trunk - Bug #8204][Open] ObjectSpace.each_object(Bignum) can generate Bignums that are to small to be Bignums — "Hanmac (Hans Mackowiak)" <hanmac@...>
5 messages
2013/04/02
[#53914] [ruby-trunk - Feature #8206][Open] Should Ruby core implement String#blank? — "sam.saffron (Sam Saffron)" <sam.saffron@...>
10 messages
2013/04/03
[#53922] [ruby-trunk - Bug #8208][Open] Raise cached exceptions for nonblocking IO to avoid allocation/stack-copying costs — "headius (Charles Nutter)" <headius@...>
7 messages
2013/04/03
[#54349] [ruby-trunk - Bug #8208] Raise cached exceptions for nonblocking IO to avoid allocation/stack-copying costs
— "headius (Charles Nutter)" <headius@...>
2013/04/16
[#54374] Re: [ruby-trunk - Bug #8208] Raise cached exceptions for nonblocking IO to avoid allocation/stack-copying costs
— Eric Wong <normalperson@...>
2013/04/17
"headius (Charles Nutter)" <headius@headius.com> wrote:
[#53950] [ruby-trunk - Bug #8211][Open] Performance regression of method calls — "dunric (David Unric)" <dunric29a@...>
9 messages
2013/04/03
[#53974] [ruby-trunk - Feature #8215][Open] Support accessing Fiber-locals and backtraces for a Fiber — "halorgium (Tim Carey-Smith)" <ruby-lang-bugs@...>
14 messages
2013/04/03
[#54023] [ruby-trunk - Feature #8223][Open] Make Matrix more omnivorous. — "boris_stitnicky (Boris Stitnicky)" <boris@...>
9 messages
2013/04/05
[#54031] Question about r39944 — Aaron Patterson <tenderlove@...>
Hi,
9 messages
2013/04/05
[#54032] Re: Question about r39944
— "NARUSE, Yui" <naruse@...>
2013/04/05
Even if test directory should be on the load path on test-all, you should
[#54095] [ruby-trunk - Feature #8237][Open] Logical method chaining via inferred receiver — "wardrop (Tom Wardrop)" <tom@...>
34 messages
2013/04/08
[#54097] [ruby-trunk - Feature #8237] Logical method chaining via inferred receiver
— "rosenfeld (Rodrigo Rosenfeld Rosas)" <rr.rosas@...>
2013/04/08
[#54175] [ruby-trunk - Bug #8254][Open] Ruby segfaults on second SystemStackError from parser — "charliesome (Charlie Somerville)" <charlie@...>
3 messages
2013/04/11
[#54185] [CommonRuby - Feature #8257][Open] Exception#cause to carry originating exception along with new one — "headius (Charles Nutter)" <headius@...>
43 messages
2013/04/11
[#54629] Re: [CommonRuby - Feature #8257][Open] Exception#cause to carry originating exception along with new one
— SASADA Koichi <ko1@...>
2013/04/27
(2013/04/12 1:40), headius (Charles Nutter) wrote:
[#54637] Re: [CommonRuby - Feature #8257][Open] Exception#cause to carry originating exception along with new one
— Charles Oliver Nutter <headius@...>
2013/04/27
On Sat, Apr 27, 2013 at 5:19 PM, SASADA Koichi <ko1@atdot.net> wrote:
[#54196] Encouraging use of CommonRuby — Charles Oliver Nutter <headius@...>
I think we need to do more to encourage the use of the CommonRuby
20 messages
2013/04/11
[#54200] Re: Encouraging use of CommonRuby
— Marc-Andre Lafortune <ruby-core-mailing-list@...>
2013/04/11
Hi,
[#54214] Re: Encouraging use of CommonRuby
— Charles Oliver Nutter <headius@...>
2013/04/12
On Thu, Apr 11, 2013 at 3:50 PM, Marc-Andre Lafortune
[#54211] Re: Encouraging use of CommonRuby
— "NARUSE, Yui" <naruse@...>
2013/04/12
As far as I understand, what is CommonRuby and the process over CommonRuby
[#54215] Re: Encouraging use of CommonRuby
— Charles Oliver Nutter <headius@...>
2013/04/12
On Thu, Apr 11, 2013 at 11:25 PM, NARUSE, Yui <naruse@airemix.jp> wrote:
[#54220] Re: Encouraging use of CommonRuby
— "NARUSE, Yui" <naruse@...>
2013/04/12
(2013/04/12 16:40), Charles Oliver Nutter wrote:
[#54232] Re: Encouraging use of CommonRuby
— Charles Oliver Nutter <headius@...>
2013/04/12
On Fri, Apr 12, 2013 at 8:08 AM, NARUSE, Yui <naruse@airemix.jp> wrote:
[#54201] Has ObjectSpace changed recently? — Dave Thomas <dave@...>
I just noticed that in 2.0, I see this:
5 messages
2013/04/11
[#54207] [CommonRuby - Feature #8258][Open] Dir#escape_glob — "steveklabnik (Steve Klabnik)" <steve@...>
15 messages
2013/04/12
[#54266] [CommonRuby - Feature #8258] Dir#escape_glob
— "rkh (Konstantin Haase)" <me@...>
2013/04/14
[#54227] [CommonRuby - Feature #8258] Dir#escape_glob
— "rkh (Konstantin Haase)" <me@...>
2013/04/12
[#54218] [CommonRuby - Feature #8259][Open] Atomic attributes accessors — "funny_falcon (Yura Sokolov)" <funny.falcon@...>
43 messages
2013/04/12
[#63015] [CommonRuby - Feature #8259] Atomic attributes accessors
— headius@...
2014/06/09
Issue #8259 has been updated by Charles Nutter.
[#63016] Re: [CommonRuby - Feature #8259] Atomic attributes accessors
— Eric Wong <normalperson@...>
2014/06/09
I'm not sure if setting the attribute on the ivar is a good way to go.
[#54333] Requesting Commit Access — Aman Gupta <ruby@...1.net>
Hello ruby-core,
16 messages
2013/04/16
[#54368] Re: Requesting Commit Access
— Yukihiro Matsumoto <matz@...>
2013/04/16
Hi,
[#54415] [ruby-trunk - Bug #8286][Open] Can't decode non-MIME Base64 — "adacosta (Alan Da Costa)" <alandacosta@...>
10 messages
2013/04/17
[#54459] [CommonRuby - Feature #8291][Open] Allow retrieving the root Fiber of a Thread — "halorgium (Tim Carey-Smith)" <ruby-lang@...>
5 messages
2013/04/19
[#54473] [Backport 200 - Backport #8299][Open] Minor error in float parsing — "bobjalex (Bob Alexander)" <bobjalex@...>
27 messages
2013/04/19
[#54549] [ruby-trunk - Bug #8299] Minor error in float parsing
— "phasis68 (Heesob Park)" <phasis@...>
2013/04/24
[#54496] [ruby-trunk - Bug #8299] Minor error in float parsing
— "naruse (Yui NARUSE)" <naruse@...>
2013/04/22
[#54509] [ruby-trunk - Bug #8310][Open] resque-web crashes with segfault on Ruby 2.0.0-p0 only, Resque 1.24.1, Redis 2.6.12 — "vaharoni (Amit Aharoni)" <amit.sites@...>
5 messages
2013/04/22
[#54559] [ruby-trunk - Feature #8321][Open] Ripper: I would like coordinates for keywords — "ericp (Eric Promislow)" <eric.promislow@...>
7 messages
2013/04/24
[#54606] Plan to the first 2.0.0 patchlevel release. — Tomoyuki Chikanaga <nagachika00@...>
Hello, Rubyists.
8 messages
2013/04/26
[#54743] Re: Plan to the first 2.0.0 patchlevel release.
— Marc-Andre Lafortune <ruby-core-mailing-list@...>
2013/05/02
Hi,
[#54815] Re: Plan to the first 2.0.0 patchlevel release.
— Aman Gupta <ruby@...1.net>
2013/05/06
Could you please backport the following:
[#54621] [ruby-trunk - Feature #8339][Open] Introducing Geneartional Garbage Collection for CRuby/MRI — "ko1 (Koichi Sasada)" <redmine@...>
43 messages
2013/04/27
[#54643] [ruby-trunk - Feature #8339] Introducing Geneartional Garbage Collection for CRuby/MRI
— "authorNari (Narihiro Nakamura)" <authorNari@...>
2013/04/28
[#54649] Re: [ruby-trunk - Feature #8339] Introducing Geneartional Garbage Collection for CRuby/MRI
— SASADA Koichi <ko1@...>
2013/04/28
(2013/04/28 9:23), authorNari (Narihiro Nakamura) wrote:
[#54770] Re: [ruby-trunk - Feature #8339] Introducing Geneartional Garbage Collection for CRuby/MRI
— Narihiro Nakamura <authornari@...>
2013/05/04
2013/4/28 SASADA Koichi <ko1@atdot.net>:
[#54772] Re: [ruby-trunk - Feature #8339] Introducing Geneartional Garbage Collection for CRuby/MRI
— SASADA Koichi <ko1@...>
2013/05/04
(2013/05/04 12:08), Narihiro Nakamura wrote:
[#54813] Re: [ruby-trunk - Feature #8339] Introducing Geneartional Garbage Collection for CRuby/MRI
— Tanaka Akira <akr@...>
2013/05/06
2013/5/4 SASADA Koichi <ko1@atdot.net>:
[#54816] Re: [ruby-trunk - Feature #8339] Introducing Geneartional Garbage Collection for CRuby/MRI
— SASADA Koichi <ko1@...>
2013/05/06
(2013/05/06 11:50), Tanaka Akira wrote:
[#54822] Re: [ruby-trunk - Feature #8339] Introducing Geneartional Garbage Collection for CRuby/MRI
— Tanaka Akira <akr@...>
2013/05/06
2013/5/6 SASADA Koichi <ko1@atdot.net>:
[#54706] [ruby-trunk - Feature #8339] Introducing Geneartional Garbage Collection for CRuby/MRI
— "sam.saffron (Sam Saffron)" <sam.saffron@...>
2013/04/30
[#54657] Re: [ruby-trunk - Feature #8339][Open] Introducing Geneartional Garbage Collection for CRuby/MRI
— Magnus Holm <judofyr@...>
2013/04/28
On Sat, Apr 27, 2013 at 8:19 PM, ko1 (Koichi Sasada)
[#54662] Re: [ruby-trunk - Feature #8339][Open] Introducing Geneartional Garbage Collection for CRuby/MRI
— SASADA Koichi <ko1@...>
2013/04/28
(2013/04/28 21:40), Magnus Holm wrote:
[#54669] Re: [ruby-trunk - Feature #8339][Open] Introducing Geneartional Garbage Collection for CRuby/MRI
— SASADA Koichi <ko1@...>
2013/04/28
(2013/04/28 23:34), SASADA Koichi wrote:
[#54671] Re: [ruby-trunk - Feature #8339][Open] Introducing Geneartional Garbage Collection for CRuby/MRI
— Magnus Holm <judofyr@...>
2013/04/28
On Sun, Apr 28, 2013 at 6:07 PM, SASADA Koichi <ko1@atdot.net> wrote:
[#54672] Re: [ruby-trunk - Feature #8339][Open] Introducing Geneartional Garbage Collection for CRuby/MRI
— SASADA Koichi <ko1@...>
2013/04/28
(2013/04/29 1:19), Magnus Holm wrote:
[#54673] Re: [ruby-trunk - Feature #8339][Open] Introducing Geneartional Garbage Collection for CRuby/MRI
— Magnus Holm <judofyr@...>
2013/04/28
On Sun, Apr 28, 2013 at 6:29 PM, SASADA Koichi <ko1@atdot.net> wrote:
[#54676] Re: [ruby-trunk - Feature #8339][Open] Introducing Geneartional Garbage Collection for CRuby/MRI
— Eric Wong <normalperson@...>
2013/04/28
"ko1 (Koichi Sasada)" <redmine@ruby-lang.org> wrote:
[#54712] [ruby-trunk - Feature #8339] Introducing Geneartional Garbage Collection for CRuby/MRI
— "sam.saffron (Sam Saffron)" <sam.saffron@...>
2013/04/30
[#54665] [ruby-trunk - Bug #8344][Open] Status of Psych and Syck — "Eregon (Benoit Daloze)" <redmine@...>
18 messages
2013/04/28
[ruby-core:54089] Re: [ruby-trunk - Feature #8223] Make Matrix more omnivorous.
From:
Zachary Scott <zachary@...>
Date:
2013-04-07 20:43:34 UTC
List:
ruby-core #54089
Hi Boris, I think it takes too long to read through all of your
messages, so best to define a smaller proposal with exact details for
each feature you want.
On Sat, Apr 6, 2013 at 4:33 PM, boris_stitnicky (Boris Stitnicky)
<boris@iis.sinica.edu.tw> wrote:
>
> Issue #8223 has been updated by boris_stitnicky (Boris Stitnicky).
>
>
> So with another apology, I will use this space to write down a few more remarks so that I do not forget about them. My line of thinking was as follows: The first step to the systematic solution of this problem would be to generalize zero. It means that the matrix elements would be required to be of a class that has #zero method defined. As for Matrix.zero and Matrix.empty, I think that there should be an option to tell them what this zero is (or tell them the class that has #zero defined). Or perhaps we could play the abstract algebra terminology and call it "additive_identity_element" instead of "zero". That would mean that Matrix would require its elements to comply with at least monoid definition for matrix addition and multiplication, and monoids necessarily need to have the additive identity element defined.
> ----------------------------------------
> Feature #8223: Make Matrix more omnivorous.
> https://bugs.ruby-lang.org/issues/8223#change-38316
>
> Author: boris_stitnicky (Boris Stitnicky)
> Status: Open
> Priority: Normal
> Assignee:
> Category:
> Target version:
>
>
> Let's imagine a class Metre, whose instances represent physical magnitudes in metres.
>
> class Metre
> attr_reader :magnitude
> def initialize magnitude; @magnitude = magnitude end
> def to_s; magnitude.to_s + ".m" end
> end
>
> Let's say that metres can be multiplied by a number:
>
> class Metre
> def * multiplicand
> case multiplicand
> when Numeric then Metre.new( magnitude * multiplicand )
> else
> raise "Metres can only be multiplied by numbers, multiplication by #{multiplicand.class} attempted!"
> end
> end
> end
>
> And that they can be summed up with other magnitudes in metres, but, as a feature,
> not with numbers (apples, pears, seconds, kelvins...).
>
> class Metre
> def + summand
> case summand
> when Metre then Metre.new( magnitude + summand.magnitude )
> else
> raise "Metres can only be summed with metres, summation with #{summand.class} attempted!"
> end
> end
> end
>
> Now with one more convenience constructor Numeric#m:
>
> class Numeric
> def m; Metre.new self end
> end
>
> We can write expressions such as
>
> 3.m + 5.m
> #=> 8.m
> 3.m * 2
> #=> 6.m
>
> And with defined #coerce:
>
> class Metre
> def coerce other; [ self, other ] end
> end
>
> Also this expression is valid:
>
> 2 * 3.m
> #=> 6.m
>
> Before long, the user will want to make a matrix of magnitudes:
>
> require 'matrix'
> mx = Matrix.build 2, 2 do 1.m end
> #=> Matrix[[1.m, 1.m], [1.m, 1.m]]
>
> It works, but the joy does not last long. The user will fail miserably if ze wants to perform matrix multiplication:
>
> cv = Matrix.column_vector [1, 1]
> mx * cv
> #=> RuntimeError: Metres can only be summed with metres, summation with Fixnum attempted!
> # where 2.m would be expected
>
> In theory, everything should be O.K., since Metre class has both metre summation and multiplication by a number defined. The failure happens due to the internal workings of the Matrix class, which assumes that the elements can be summed together with numeric 0. But it is a feature of metres, that they are picky and allow themselves to be summed only with other Metre instances.
>
> In my real physical units library that I have written, I have solved this problem by
> defining an er zero object that produces the expected result, when summed with objects, that would otherwise not lend themselves to summation with ordinary numeric 0,
> and patching the Matrix class so that it uses this er zero instead of the ordinary one.
>
> But this is not a very systematic solution. Actually, I think that the Matrix class would be more flexible, if, instead of simply using 0, it asked the elements of the matrix what their zero is, as in:
>
> class << Metre
> def zero; new 0 end
> end
>
> But of course, that would also require that ordinary numeric classes can tell what their zero is, as in:
>
> def Integer.zero; 0 end
> def Float.zero; 0.0 end
> def Complex.zero; Complex 0.0, 0.0 end
> # etc.
>
> I think that this way of doing things (that is, having #zero methods in numeric classes and making Matrix actually require the class of the objects in it to have public class method #zero defined) would make everything more consistent and more algebra-like. I am having this problem for already almost half a year, but I only gathered courage today to encumber you guys with this proposal. Please don't judge me harshly for it. I have actually already seen something like this, in particular with bigdecimal's Jacobian (http://ruby-doc.org/stdlib-2.0/libdoc/bigdecimal/rdoc/Jacobian.html), which requires that the object from which the Jacobian is computed implements methods #zero, #one, #two etc. Sorry again.
>
>
> --
> http://bugs.ruby-lang.org/
>