• Tyro[a.c.edwards] <no.spam home.com> Jun 27 2010
• Lutger <lutger.blijdestijn gmail.com> Jun 27 2010
• Tyro[a.c.edwards] <no.spam home.com> Jun 27 2010
• "Simen kjaeraas" <simen.kjaras gmail.com> Jun 27 2010
• Lutger <lutger.blijdestijn gmail.com> Jun 27 2010
• Jacob Carlborg <doob me.com> Jun 27 2010

Tyro[a.c.edwards] <no.spam home.com> writes:

Andrei,

I must say that the reading is absolutely enjoyable. I do have one
question regarding the StackImpl example on page 234. Are you forecasting
future functionality that arrays will support with your
use of .empty, .back, and .popBack or am I too naïve to understand
that I need to implement this functionality in order for your example
to compile?

Lutger <lutger.blijdestijn gmail.com> writes:

 wrote:

 Andrei,
 
 I must say that the reading is absolutely enjoyable. I do have one
 question regarding the StackImpl example on page 234. Are you forecasting
 future functionality that arrays will support with your use of .empty, .back,
 and .popBack or am I too na�ve to understand that I need to implement this
 functionality in order for your example to compile?


These functions are implemented in std.array, you only need to import that 
module.

Tyro[a.c.edwards] <no.spam home.com> writes:

== Quote from Lutger (lutger.blijdestijn gmail.com)'s article
  wrote:
 Andrei,

 I must say that the reading is absolutely enjoyable. I do have one
 question regarding the StackImpl example on page 234. Are you




 future functionality that arrays will support with your use of




 and .popBack or am I too na�ve to understand that I need to




 functionality in order for your example to compile?




 module.


Thanks.

"Simen kjaeraas" <simen.kjaras gmail.com> writes:

Lutger <lutger.blijdestijn gmail.com> wrote:

  wrote:

 Andrei,

 I must say that the reading is absolutely enjoyable. I do have one
 question regarding the StackImpl example on page 234. Are you  =




 forecasting
 future functionality that arrays will support with your use of .empty=





 .back,
 and .popBack or am I too na=EF=BF=BDve to understand that I need to i=





 this
 functionality in order for your example to compile?


 These functions are implemented in std.array, you only need to import =



 that
 module.


Now why aren't those included by default? Sure, they're not always
necessary, but they are what makes arrays into ranges, a property that
has touted extensively.

-- =

Simen

Lutger <lutger.blijdestijn gmail.com> writes:

Simen kjaeraas wrote:

 Lutger <lutger.blijdestijn gmail.com> wrote:
 
  wrote:

 Andrei,

 I must say that the reading is absolutely enjoyable. I do have one
 question regarding the StackImpl example on page 234. Are you
 forecasting
 future functionality that arrays will support with your use of .empty,
 .back,
 and .popBack or am I too na�ve to understand that I need to implement
 this
 functionality in order for your example to compile?


 These functions are implemented in std.array, you only need to import
 that
 module.


 Now why aren't those included by default? Sure, they're not always
 necessary, but they are what makes arrays into ranges, a property that
 has touted extensively.
 


A public import of std.array by std.algorithm could do the trick.

Jacob Carlborg <doob me.com> writes:

On 2010-06-27 14:42, Lutger wrote:
 Simen kjaeraas wrote:

 Lutger<lutger.blijdestijn gmail.com>  wrote:

   wrote:

 Andrei,

 I must say that the reading is absolutely enjoyable. I do have one
 question regarding the StackImpl example on page 234. Are you
 forecasting
 future functionality that arrays will support with your use of .empty,
 .back,
 and .popBack or am I too na�ve to understand that I need to implement
 this
 functionality in order for your example to compile?


 These functions are implemented in std.array, you only need to import
 that
 module.


 Now why aren't those included by default? Sure, they're not always
 necessary, but they are what makes arrays into ranges, a property that
 has touted extensively.


 A public import of std.array by std.algorithm could do the trick.


Or the opposite, depending how you look at it.

-- 
/Jacob Carlborg