-
```
I suggest adopting some (written) coding conventions to keep the source
easier to read, and to avoid some common pitfalls that occur when the
compiler is the only syntax verification step.
Sun ha…
-
Similar to https://github.com/eugeneloza/castle-engine/blob/master/doc/miscellaneous_notes/coding_conventions.txt
-
This is the **summary issue** for the `unsupported_fn_ptr_calling_conventions` future-compatibility warning. The goal of this page is describe why this change was made and how you can fix code that is…
-
As we keep deciding on how tests should be constructed, naming schemes, formatting tools, docstrings, etc. we should have a markdown text file (a "CONTRIBUTING.md") to define our guidelines for writin…
-
```
I suggest adopting some (written) coding conventions to keep the source
easier to read, and to avoid some common pitfalls that occur when the
compiler is the only syntax verification step.
Sun ha…
-
@regexps/owners
Starts here https://github.com/regexps/regex-block-comment/issues/1
@jonschlinkert apologize in advance if something, but I think here is the correct place for it. I cant realize an…
-
```
I suggest adopting some (written) coding conventions to keep the source
easier to read, and to avoid some common pitfalls that occur when the
compiler is the only syntax verification step.
Sun ha…
-
### Description:
The code base has been under development for several years, and over time different conventions have been used for function names. That can make it a bit confusing to find _which_ …
-
### Issue
I work on a full stack codebase with aider: solidity, golang and react/typescript. This is a somewhat challenging environment for aider right now — tree-sitter in aider isn’t really set up …
-
Check all the names in the project for naming conventions