| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
Based on looking at the git logs, add copyright notices to files which
were missing them, assuming the copyright belongs to people who made major
contributions to each file.
Some assumptions were made as to who to assign the copyright to, such as,
what copyright assignment did the contributor make in other files added in
the same commit? What email address did they use to make the commit? What
copyright assignment did they make in other commits using the same email
address?
|
| |
|
|
|
|
| |
This adds a SPDX-License-Identifier comment to all files that are part
of GJS, part of its unit tests, or auxiliary tools. (Except for some
files like the debugger scripts that don't support comments.)
|
| |
|
|
|
|
|
| |
This rule exists because Chromium doesn't want certain C++ standard
library features in their codebase since they have implemented their own
alternatives. This rule shouldn't apply to codebases that aren't
Chromium.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously #include statements were a bit of a mess across the codebase.
This commit is the result of a pass by the IWYU (Include What You Use)
tool, which suggests headers to add or remove based on what is in the
file, and can also suggest forward-declaring classes instead of
including their headers, if they are only used as a pointer in a
particular file. Cleaning this up should in general speed up compile
times.
IWYU isn't perfect, it produces a number of false positives, so we don't
try to automate this process and we don't accept all of its
recommendations. We do add a script and configuration file to the tools/
directory so that IWYU can be every so often in the future.
We also clean up all the includes according to a consistent style, which
is now described clearly in the C++ style guide.
|
| |
|
|
|
|
|
|
|
|
| |
We're going to just use the Google C++ coding style, so remove our
customizations. (We do still allow lines a little bit longer than the
limit that we give to clang-format, since sometimes clang-format will
format a line longer than 80 characters if the alternative is worse.)
[skip cpplint] since this will of course introduce many more linter
errors.
|
|
|
This disables the cpplint rules that cause the most problems with our
existing style. It's not possible to customize the rules, so
unfortunately this means that, for example, braces aren't checked at all,
because the cpplint brace style disagrees with our existing brace style.
[skip cpplint] because some messages changed (e.g. line length).
Closes #137.
|
