If you had money to place for a bounty, what would you choose?

[Iain Buclaw]

On Nov 30, 2013 3:01 AM, "Nick" <nmsmith65 at gmail.com> wrote:
>
> On Friday, 29 November 2013 at 15:23:13 UTC, Andrei Alexandrescu wrote:
>>
>> On 11/29/13 5:43 AM, Manu wrote:
>>>
>>> * ARC
>>> * rvalue -> ref
>>> * virtual-by-default
>>> * GC improvements
>>> * AA fixes
>>
>>
>> These are good themes but a conversation with one of the bountysource
founders revealed to me that smaller, precise tasks for moderate amounts
tend to do better than large projects that are only partially specified,
even for large amounts.
>>
>> We should break each of these down into bite-sized bugzilla issues.
>>
>>
>> Andrei
>
>
> A bite-sized GC-related improvement is the @nogc attribute I've been
craving for for quite some time. See:
https://d.puremagic.com/issues/show_bug.cgi?id=5219
>
> If I had money, I'd be putting it on this for sure. For system and game
programmers it's a godsend, and it will put some C++ fanatics at ease with
D's GC. With this feature I can protect the critical sections of my code
with a firm guarantee that I won't see any unexpected activity from the GC.

But how do you expect this to be implemented? Implicitly putting
GC.disable/GC.enable at the prologue / epilogue of a function?

Regards
-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20131130/f6c833d3/attachment.html>