Re: Tuple unpacking syntax [Was: Re: Multiple return values...]

2012-03-14 Thread Manu
I'm encouraged to see that every person in this thread so far seems to feel the same way as me regarding the syntax. On 14 March 2012 05:25, Derek Parnell wrote: > On Wed, 14 Mar 2012 13:33:18 +1100, Kevin Cox > wrote: > >> (int i,,float f) = intBoringFloat(); >> > > For what its worth, the Eu

Re: Tuple unpacking syntax [Was: Re: Multiple return values...]

2012-03-14 Thread RivenTheMage
On Wednesday, 14 March 2012 at 02:33:29 UTC, Kevin Cox wrote: Kind of unrelated but I think that it is important to have a way to ignore values also. Leaving them bank would sufice. (int i,,float f) = intBoringFloat(); or (int i, null, float f) = intBoringFloat(); or (int i, void, float f

Re: Tuple unpacking syntax [Was: Re: Multiple return values...]

2012-03-14 Thread Robert Jacques
On Wed, 14 Mar 2012 03:52:55 -0500, Manu wrote: I'm encouraged to see that every person in this thread so far seems to feel the same way as me regarding the syntax. On 14 March 2012 05:25, Derek Parnell wrote: On Wed, 14 Mar 2012 13:33:18 +1100, Kevin Cox wrote: (int i,,float f) = intBo

Re: Tuple unpacking syntax [Was: Re: Multiple return values...]

2012-03-14 Thread Manu
On 14 March 2012 15:17, Robert Jacques wrote: > But there's a reason we use /// instead of ⫻; we shouldn't require custom > keyboard mappings in order to program efficiently in D. > Hold that thought, I think you're missing a major franchising opportunity right there... D branded 'pro-codah' key

Re: Tuple unpacking syntax [Was: Re: Multiple return values...]

2012-03-14 Thread foobar
On Wednesday, 14 March 2012 at 13:17:47 UTC, Robert Jacques wrote: But there's a reason we use /// instead of ⫻; we shouldn't require custom keyboard mappings in order to program efficiently in D. Aren't we supposed to be moving towards more natural interfaces in computing? I'm sure that onc

More on multiple return values [was: Re: Multiple return values]

2012-01-04 Thread bearophile
I don't like 'out' function arguments, from a logic point of view they feel unnatural and backwards (while 'ref' arguments are meaningful from a computer science point of view). I'd even like to see 'out' arguments deprecated when multiple return values are introduced as a bit of built-in syntax

Re: More on multiple return values [was: Re: Multiple return values]

2012-01-05 Thread Gor Gyolchanyan
+1 no comments :-) On Thu, Jan 5, 2012 at 4:32 AM, bearophile wrote: > I don't like 'out' function arguments, from a logic point of view they feel > unnatural and backwards (while 'ref' arguments are meaningful from a computer > science point of view). I'd even like to see 'out' arguments depr

<    1   2   3