On Saturday, August 04, 2012 15:09:50 Alex Rønne Petersen wrote:
> On 04-08-2012 04:57, Jonathan M Davis wrote:
> > On Saturday, August 04, 2012 04:44:12 Alex Rønne Petersen wrote:
> >>> It's been discussed a time or two that we should have an incubator
> >>> project
> >>> for Phobos where potentia
On 04-08-2012 04:57, Jonathan M Davis wrote:
On Saturday, August 04, 2012 04:44:12 Alex Rønne Petersen wrote:
It's been discussed a time or two that we should have an incubator project
for Phobos where potential Phobos modules go to be used and ironed out
before actually being reviewed for inclu
On Saturday, August 04, 2012 11:25:35 Paulo Pinto wrote:
> Where should it be hosted, github?
Probably. That's where we're putting everything else.
- Jonathan M Davis
Am 04.08.2012 04:42, schrieb Jonathan M Davis:
On Saturday, August 04, 2012 02:37:07 Stefan Scholl wrote:
bearophile wrote:
Caligo:
When are allocators going to be ready?
Direct experience shows me that once things are in Phobos, it's
not easy to fix their interface/API. Andrei fears of bre
On Saturday, August 04, 2012 04:44:12 Alex Rønne Petersen wrote:
> > It's been discussed a time or two that we should have an incubator project
> > for Phobos where potential Phobos modules go to be used and ironed out
> > before actually being reviewed for inclusion in Phobos. But it's never
> > m
On 04-08-2012 04:42, Jonathan M Davis wrote:
On Saturday, August 04, 2012 02:37:07 Stefan Scholl wrote:
bearophile wrote:
Caligo:
When are allocators going to be ready?
Direct experience shows me that once things are in Phobos, it's
not easy to fix their interface/API. Andrei fears of break
On Saturday, August 04, 2012 02:37:07 Stefan Scholl wrote:
> bearophile wrote:
> > Caligo:
> >> When are allocators going to be ready?
> >
> > Direct experience shows me that once things are in Phobos, it's
> > not easy to fix their interface/API. Andrei fears of breaking
>
> Go's solution are e
On Saturday, August 04, 2012 02:37:07 Stefan Scholl wrote:
> bearophile wrote:
> > Caligo:
> >> When are allocators going to be ready?
> >
> > Direct experience shows me that once things are in Phobos, it's
> > not easy to fix their interface/API. Andrei fears of breaking
>
> Go's solution are e
bearophile wrote:
> Caligo:
>> When are allocators going to be ready?
>
> Direct experience shows me that once things are in Phobos, it's
> not easy to fix their interface/API. Andrei fears of breaking
Go's solution are experimental packages. You can always use them,
but you know that they wil
On 2012-08-03 21:44, bearophile wrote:
Direct experience shows me that once things are in Phobos, it's not easy
to fix their interface/API. Andrei fears of breaking changes, so even
small API improvements of Phobos stuff written last year are refused.
See as example:
One option would be to cre
On Friday, 3 August 2012 at 19:44:22 UTC, bearophile wrote:
Caligo:
When are allocators going to be ready?
Direct experience shows me that once things are in Phobos, it's
not easy to fix their interface/API. Andrei fears of breaking
changes, so even small API improvements of Phobos stuff wr
Caligo:
When are allocators going to be ready?
Direct experience shows me that once things are in Phobos, it's
not easy to fix their interface/API. Andrei fears of breaking
changes, so even small API improvements of Phobos stuff written
last year are refused. See as example:
http://d.pure
When are allocators going to be ready?
On Fri, Aug 3, 2012 at 10:31 AM, Andrei Alexandrescu
wrote:
> ... with a few stats. Vote up!
>
> http://www.reddit.com/r/programming/comments/xm5y0/d_260_released_d_programming_language/
>
>
> Andrei
On Fri, 03 Aug 2012 11:31:27 -0400
Andrei Alexandrescu wrote:
> ... with a few stats. Vote up!
>
> http://www.reddit.com/r/programming/comments/xm5y0/d_260_released_d_programming_language/
>
>
> Andrei
Wow, that's much more positive towards D than Reddit used to be. Used
to be much more mixed
... with a few stats. Vote up!
http://www.reddit.com/r/programming/comments/xm5y0/d_260_released_d_programming_language/
Andrei
15 matches
Mail list logo