Josh Goebel

> aliases like nord4 should be ignored by templates. Yes that's the idea. They'd only exist as a convenience for scheme authors. I think in many other cases one might...

> I suggest also including diff_modified Sure. I purposely wasn't being exhaustive... obviously an official list would need to be created if we are to go this direction... and it...

I'd say: - first get buy-in on the whole proposal at a high-level - create an official list - run that list by template maintainers (who will likely suggest additions)...

> require to create a simple linting tool based on some of the builders I'm not sure why it wouldn't just *be* the builder... CI: - select a template that...

> ffffff is it "variable" name or color? Well it could technically be either... if there was an `ffffff` variable, it's a variable, otherwise it's a color - that was...

> that's not worth of breaking backward-compatibility It wouldn't since no aliases exist yet, there are no naming conflicts yet. The `#` would only be necessarily in the case of...

> totally disabling colors without # would break backward-compatibility I was never suggesting that. > adding resolution algorithm ... builder logic It's quite trivial I assure you... few lines. But...

> but every of those "two lines" here and there would be a PITA if implementing builder from scratch I've written such things from scratch before, it's simply not that...

@belak Kind of waiting for your high-level thoughts before I whip up a quick proof of concept and fix Nord to see how all this might work in practice. :)

> but why to do it at all if same problem could be solved without doing it? It has to be done one way or the other - which requires...