3 ms·
Again, not if you enforce a code style which nearly always should in a professional context. Such a mistakes is easy for a linter to pick up on so that the cod
by cardanome 4y ago
Again, not if you enforce a code style which nearly always should in a professional context.
Such a mistakes is easy for a linter to pick up on so that the code would never be merged in the first place.
- overthrow 4y agoHow does the linter treat 'get_file_system' and 'get_filesystem'? Which one would be flagged as an error?
- deleted 4y ago[deleted]
- ptramo 4y agoThe one that doesn't match the declaration.
- overthrow 4y agoAn earlier comment says: > It's so external dependencies don't have to infect your codebase. So you can actually apply a consistent code style within your project. Say an external dependency has a declaration called 'getFileSystem', and in my Nim codebase I refer to it as 'get_file_system', but last year someone accidentally committed 'get_filesystem'. In this case neither usage matches the declaration. Does the linter flag both spellings because they don't match 'getFileSystem'? EDIT: And what about reflection? If someone wrote `newCall("get_filesystem")`, will the linter fix that too?