On Sun, 16 Dec 2018 16:32:50 -0500, Steven Schveighoffer wrote:
> On 12/16/18 2:42 PM, Neia Neutuladh wrote:
>> 1. Move your aggregates above the `@nogc nothrow pure:` line
>> 2. Move your aggregates outside the `@nogc nothrow pure {}` block
>> 3. Mark functions `@nogc nothrow pure` individually
> 
> None of those are good options.

I mean, yes, they're not super awesome. But it's also not like this is some unthinkably horrific thing that we're forced to use curly braces or reorder declarations sometimes -- we've been dealing with this with functions for years.

Unless there's some widespread tip running around to put a function inside a struct to reset @nogc and friends?

On 17/12/2018 8:39 AM, Neia Neutuladh wrote:
> On Mon, 17 Dec 2018 07:20:29 +1300, rikki cattermole wrote:
>> If it doesn't match bug report.
> 
> The bug report is six years old and has not had an official response. I
> submitted a PR and one of the reviewers recommended that I search the
> newsgroup and github PR comments and the like to see if Walter had said
> anything on the topic.

You did the right thing making noise about it, though a link to the issue would have been better  :)

On Mon, 17 Dec 2018 13:45:51 +1300, rikki cattermole wrote:
> You did the right thing making noise about it, though a link to the issue would have been better  :)

Thank you.

Issue: https://issues.dlang.org/show_bug.cgi?id=7616