RFC: reference counted Throwable

[luka8088 via Digitalmars-d]

On 21.9.2014. 22:57, Peter Alexander wrote:
> On Sunday, 21 September 2014 at 19:36:01 UTC, Nordlöw wrote:
>> On Friday, 19 September 2014 at 15:32:38 UTC, Andrei Alexandrescu wrote:
>>> Please chime in with thoughts.
>>
>> Why don't we all focus our efforts on upgrading the current GC to a
>> state-of-the GC making use of D's strongly typed memory model before
>> discussing these things?
>
> GC improvements are critical, but...
>
> "As discussed, having exception objects being GC-allocated is clearly a
> large liability that we need to address. They prevent otherwise careful
> functions from being @nogc so they affect even apps that otherwise would
> be okay with a little litter here and there."
>
> No improvements to the GC can fix this. @nogc needs to be usable,
> whether you are a GC fan or not.

I think that what is being suggested is that upgrading GC would 
widespread the point of view on what can and should be done.

For example, now that ranges and mixins exist great ideas comes to mind, 
and without them we can only guess. I think that GC is in the same position.