On Thursday, 22 December 2016 at 10:35:23 UTC, Basile B. wrote:
> On Thursday, 22 December 2016 at 10:11:19 UTC, Basile B. wrote:
>> On Thursday, 22 December 2016 at 04:11:54 UTC, Chris Wright wrote:
>>> While we're talking about this, this proposal breaks any string mixin that mixes in an identifier detected with reflection.
>>
>> RIP DIP 1007. It was too simple to be true.
>
> I see something to do to continue the DIP
>
> [...]
>
> Which means that you can use As many # as you want to escape a keyword.
> Mixins cannot introspect themselves so basically 'pound pound' will always work.
> And this is still a simple thing that can be done in the lexer.

no...it's dead, obviously whatever is the amount of #, they'll be removed when the token is patched for the first time. This just doesn't work with mixins. End of story.

On 12/22/2016 05:11 AM, Basile B. wrote:
> On Thursday, 22 December 2016 at 04:11:54 UTC, Chris Wright wrote:
>> While we're talking about this, this proposal breaks any string mixin
>> that mixes in an identifier detected with reflection.
>
> RIP DIP 1007. It was too simple to be true.

If that's the case please mark it as "Retired". -- Andrei

On Thursday, 22 December 2016 at 10:47:37 UTC, Basile B. wrote:
> End of story.

This was worth trying anyway. Especially for the "body" keyword. Personally I don't need it anymore, but it is substantial issue for newcomers wanting to use it badly for web/sci dev.

This is probably the most controversial keyword. It is a big pain for a pedant person but on the other hand it is really a non-issue among other programming problems.

I bet this case will be brought up continuously. So be prepared.

It could have been called something like "fbody" or "def". ;)

Cheers,
Piotrek

On Thursday, 22 December 2016 at 04:11:54 UTC, Chris Wright wrote:
> While we're talking about this, this proposal breaks any string mixin that mixes in an identifier detected with reflection.

http://imgur.com/NHe6k2p

On Thu, 22 Dec 2016 10:47:37 +0000, Basile B. wrote:
> no...it's dead, obviously whatever is the amount of #, they'll be removed when the token is patched for the first time. This just doesn't work with mixins. End of story.

If it's changed to `# identifier` instead of `# keyword`, you can defensively add an octothorp to any identifier you mix in. However, that would fail if someone has an identifier named `line`. And in any case it breaks existing string mixins.