Changes between Initial Version and Version 1 of Ticket #6581, comment 14
- Timestamp:
- 04/14/2018 10:05:49 PM (20 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #6581, comment 14
initial v1 1 1 I tend to agree with mjethani (and the article he refers to). Still I wonder how to turn that into an unambiguous rule for our coding style guide. Maybe something like this: 2 2 3 > Use `const` (only) for real constants (on the module/top-level) wh ose valuenot being re-assigned isn't coincidental or matter to change in the future, but would inherently break things worth to protect against.3 > Use `const` (only) for real constants (on the module/top-level) which not being re-assigned isn't coincidental or matter to change in the future, but would inherently break things worth to protect against.