Enforced Style Guide

[StealthHydra179]

sack/readme.md

Line 26 in 9ee412a

- Sack enforces a style guide to improve readability, it is left up to the implementation whether this is a default warn or error. For simplicity, the style guide will not be described in this spec, however the example code will follow it.

For consistency between sack compilers, a selection of one or the other should probably be made (like a warning).

[Bigjango13]

It would be easier for compilers to have a separate option for checking style consistency. It may be tiring for a programmer to get bogged down with minor style errors while trying to concentrate on the program itself.

[StealthHydra179]

Wouldn't it be better to have the spec state that style guide is default warning, and with a flag an error?

[Bigjango13]

Wouldn't it be better to have the spec state that style guide is default warning, and with a flag an error?

For consistency between sack compilers yes, but it's probably better to have a flag to enable the style warnings in the first place so writing and testing code can separate from cleaning it up.

[StealthHydra179]

I would make it a flag to disable warnings instead, as style warnings are something that should be followed unless explicitly ignored.

[nobody5050]

Default warn is probably best, this is a holdover from when I was first writing it