@gc attribute for bypassign @nogc

[rikki cattermole via Digitalmars-d]

On 25/07/2016 5:16 PM, Jonathan Marler wrote:
> On Monday, 25 July 2016 at 03:18:17 UTC, rikki cattermole wrote:
>> On 25/07/2016 10:13 AM, bitwise wrote:
>>> [...]
>>
>> I've been saying for a very long time we need @assumenogc attribute
>> like we have @trusted for @safe.
>
> I havent seen this assumegc propsal before, could you provide the
> definition you had in mind for it?

I've mostly kept it off hand for other regulars as I'm not really the 
best person to run with it and make it happen.

>> I have not been taken very seriously about this...
>>
>> Although I see no reason to allow GC in @assumenogc as long as it does
>> not trigger scan/collect phase of it. After all, why don't we have a
>> hint on allocation if we do or do not want it to trigger a scan?
>
> If the GC supported this mode (NoCollectionMode), what should the GC do
> when it is in this mode and an allocation is requested that can't be
> done until a collection is done?

Fail.
On Linux this should almost never happen and Windows should in theory be 
the same way.