Compiler hints, inlining and syntax consistency

[Dicebot]

On Saturday, 28 December 2013 at 15:36:56 UTC, Ola Fosheim 
Grøstad wrote:
> On Saturday, 28 December 2013 at 14:32:20 UTC, Jacob Carlborg 
> wrote:
>> Originally @ was added for some new keywords to get a new 
>> "namespace" for keywords. There was no risk of conflict with
>
> Understand. Objective-C and Python also suffers from the 
> arbitrary "@" syntax. Basically what I would like to see is 
> "@keyword" on stuff that can be hidden without making the 
> semantics less clear (so you could have a "hide/show" button in 
> your editor).

It should be #keyword than, as existing #line is closest thing to 
what you describe

> // allocate simd-aligned and 0-padded string by sacrificing 
> memory for efficiency,
> // if supported
>
> @simd string

Bad example - it impacts program semantics a lot.

> // force loop-unrolling modulo 4 in order to trigger SIMD 
> optimizations
>
> @unroll(4) for(…) {}

Same here. Such stuff is done by compiler-specific attributes or 
pragmas. It has no similarities with stuff like #foldregion and 
should not be treated same.