Re: [sage-devel] Re: matrix constructor signature clash

2015-06-20 Thread Vincent Delecroix
On 20/06/15 23:21, Nils Bruin wrote: On Saturday, June 20, 2015 at 11:55:02 AM UTC-7, Martin R wrote: Yes, that's quite clear. _matrix_constructor determines nrows (2) and ncols (3) and the ring (Symbolic Ring) and calls matrix_space.MatrixSpace(ring, nrows, ncols)(entries). This fails, since

Re: [sage-devel] Re: matrix constructor signature clash

2015-06-19 Thread Nils Bruin
On Friday, June 19, 2015 at 5:29:42 PM UTC-7, David Roe wrote: > > Another option might be to force certain construction paths to use keyword > arguments. For example, > matrix(4,4,scalar = x+y) > matrix(4,4,iterator = x+y) > David > Indeed, but then: how is this more convenient than the followin

Re: [sage-devel] Re: matrix constructor signature clash

2015-06-19 Thread David Roe
Another option might be to force certain construction paths to use keyword arguments. For example, matrix(4,4,scalar = x+y) matrix(4,4,iterator = x+y) David On Fri, Jun 19, 2015 at 11:03 AM, Nils Bruin wrote: > On Friday, June 19, 2015 at 9:10:41 AM UTC-7, Darij Grinberg wrote: >> >> > Unfortun

Re: [sage-devel] Re: matrix constructor signature clash

2015-06-19 Thread Nils Bruin
On Friday, June 19, 2015 at 9:10:41 AM UTC-7, Darij Grinberg wrote: > > > Unfortunately, this is invited by the design of sage: The "__call__" > entry > > on a parent is the main interface to element construction and since this > is > > "conversion", all kinds of wild input are allowed. > > I

Re: [sage-devel] Re: matrix constructor signature clash

2015-06-19 Thread Darij Grinberg
On Fri, Jun 19, 2015 at 5:45 PM, Nils Bruin wrote: > On Wednesday, June 17, 2015 at 7:48:15 AM UTC-7, Darij Grinberg wrote: >> >> Unfortunately, currently the ducktyping is not just in the matrix >> constructor; it is split across the three stations I mentioned (matrix >> constructor, matrix space

Re: [sage-devel] Re: matrix constructor signature clash

2015-06-19 Thread Nils Bruin
On Wednesday, June 17, 2015 at 7:48:15 AM UTC-7, Darij Grinberg wrote: > > Unfortunately, currently the ducktyping is not just in the matrix > constructor; it is split across the three stations I mentioned (matrix > constructor, matrix space, matrix class). Apparently every single of > our matri

Re: [sage-devel] Re: matrix constructor signature clash

2015-06-17 Thread Darij Grinberg
Hi Nils, On Wed, Jun 17, 2015 at 4:37 PM, Nils Bruin wrote: > On Wednesday, June 17, 2015 at 5:52:20 AM UTC-7, Darij Grinberg wrote: > Here is that response then. For the most part, matrix does work nicely and I > really appreciate the typing it saves. > > I think a good interface design pattern

Re: [sage-devel] Re: matrix constructor signature clash

2015-06-17 Thread Jeroen Demeyer
Quote of the day :-) On 2015-06-17 14:52, Darij Grinberg wrote: Ducktyping has its limits when the pond is bottomless and has frogs, chameleons, kraken, dead things and horrors unknown. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubsc