I recall from discussion a while back that various custom allocators are in the works as alternatives to the GC.

Can anyone advise on their status and give a rough idea of what will be offered?

Perhaps this should have gone in D.learn but as it's about language development, the main forum seems like the best place to open discussion.

On Friday, 23 August 2013 at 11:27:06 UTC, Joseph Rushton Wakeling wrote:
> I recall from discussion a while back that various custom allocators are in the works as alternatives to the GC.
>
> Can anyone advise on their status and give a rough idea of what will be offered?
>
> Perhaps this should have gone in D.learn but as it's about language development, the main forum seems like the best place to open discussion.

I see Andrei running away !

On Friday, 23 August 2013 at 11:30:01 UTC, deadalnix wrote:
> I see Andrei running away !

I see an upcoming drinking game at the next dconf. A shot of whiskey anytime anyone mentions allocators. :P

On 2013-08-23 13:33, Andrej Mitrovic wrote:

> I see an upcoming drinking game at the next dconf. A shot of whiskey
> anytime anyone mentions allocators. :P

It would be pretty bad if the allocator problem hasn't been solved a year from now, assuming the next dconf will be in about a year.

-- 
/Jacob Carlborg

On Friday, 23 August 2013 at 11:33:11 UTC, Andrej Mitrovic wrote:
> On Friday, 23 August 2013 at 11:30:01 UTC, deadalnix wrote:
>> I see Andrei running away !
>
> I see an upcoming drinking game at the next dconf. A shot of whiskey anytime anyone mentions allocators. :P

Or auto ref. ;)

On Friday, 23 August 2013 at 11:40:48 UTC, Namespace wrote:
> On Friday, 23 August 2013 at 11:33:11 UTC, Andrej Mitrovic wrote:
>> On Friday, 23 August 2013 at 11:30:01 UTC, deadalnix wrote:
>>> I see Andrei running away !
>>
>> I see an upcoming drinking game at the next dconf. A shot of whiskey anytime anyone mentions allocators. :P
>
> Or auto ref. ;)

Comparing to allocators, "auto ref" is only worth sip of beer. Those are pretty close to "eternal classics" state :)

On Friday, 23 August 2013 at 13:06:22 UTC, Dicebot wrote:
> On Friday, 23 August 2013 at 11:40:48 UTC, Namespace wrote:
>> On Friday, 23 August 2013 at 11:33:11 UTC, Andrej Mitrovic wrote:
>>> On Friday, 23 August 2013 at 11:30:01 UTC, deadalnix wrote:
>>>> I see Andrei running away !
>>>
>>> I see an upcoming drinking game at the next dconf. A shot of whiskey anytime anyone mentions allocators. :P
>>
>> Or auto ref. ;)
>
> Comparing to allocators, "auto ref" is only worth sip of beer. Those are pretty close to "eternal classics" state :)

As long as it is german beer... ;)

On Friday, 23 August 2013 at 11:30:01 UTC, deadalnix wrote:
>
> I see Andrei running away !

So far, this is the best description of current situation regarding allocators.

On Friday, 23 August 2013 at 11:27:06 UTC, Joseph Rushton Wakeling wrote:
> I recall from discussion a while back that various custom allocators are in the works as alternatives to the GC.
>
> Can anyone advise on their status and give a rough idea of what will be offered?

It seems you're far from being the only interested party!

Has anyone tried porting an existing allocator library from C++? Looking over the dconf proceedings, HeapLayers was mentioned as an inspiration for a future D allocators library; would a port make sense?

I remember seeing a D2 region allocator, but it appeared to be abandonware.

Assuming you have a really great allocator library, how would that work with the existing GC requiring features of D? For example, could you have all of your slicing, classes, exceptions, etc. handled by a region allocator?

-- Brian

On 23/08/13 13:29, deadalnix wrote:
> I see Andrei running away !

That was what I feared ... :-)