nothrow by default

[Les De Ridder]

On Saturday, 4 January 2020 at 21:07:03 UTC, Adam D. Ruppe wrote:
> [...]
>
> lol we could always use existing keywords like crazy:
>
> pure!false
> @nogc!true
> nothrow!default
> virtual!false
>
> or something similar.

I had this idea too (for my toy language). One potential problem 
is
@safe/@system/@trusted though, but you could just keep @trusted 
as a
separate attribute.

> [...]
>
> I also wouldn't oppose templates simply not being affected by 
> scope-level keyword attributes. That might be a winner 
> actually.... maybe. If you want it to apply to the template, 
> you'd just have to explicitly write it again. They get special 
> case because of the inference rule.

This is an interesting idea. How often do you actually want your
templates to be affected by scope-level attributes?