On Friday, 4 August 2017 at 16:32:27 UTC, 12345swordy wrote:
On Friday, 4 August 2017 at 16:27:47 UTC, Stefan Koch wrote:
On Friday, 4 August 2017 at 16:11:11 UTC, 12345swordy wrote:
On Friday, 4 August 2017 at 16:07:51 UTC, Kagamin wrote:
On Thursday, 3 August 2017 at 18:32:25 UTC, 12345swordy
wrote:
"Enable writing
compiler-enforced
patterns for any purpose:
coding standards
(e.g., many
Core Guidelines
“enforce” rules)
"
Yes, it does, right there. Are you reading the same paper
that I am?
It works only on declarations, like D.
I know that, what is your point?
It means it can't be done.
Do do recursive flow-sensitive checks, (like those needed to
enforce 'pure' or indeed '@nogc'), you'd have to write a
self-modifying meta-program.
Which you cannot do.
I wasn't thinking about recursive checking when I was talking
about enforcing code standards.
Alex
enforcing a standard on the top-level only does not really
enforce anything.
Which is why Timon asked how you'd write the code.
Because you have to try doing it to see that it is indeed not
possible to the level that is needed for those constructs.
