| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | |
|
| |\ \
| | |
| | | |
Style: Remove new line at block start, enforce line between functions, enforce braces in if and loop blocks
|
| | | |
| | |
| | |
| | |
| | | |
Using clang-tidy's `readability-braces-around-statements`.
https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I couldn't find a tool that enforces it, so I went the manual route:
```
find -name "thirdparty" -prune \
-o -name "*.cpp" -o -name "*.h" -o -name "*.m" -o -name "*.mm" \
-o -name "*.glsl" > files
perl -0777 -pi -e 's/\n}\n([^#])/\n}\n\n\1/g' $(cat files)
misc/scripts/fix_style.sh -c
```
This adds a newline after all `}` on the first column, unless they
are followed by `#` (typically `#endif`). This leads to having lots
of places with two lines between function/class definitions, but
clang-format then fixes it as we enforce max one line of separation.
This doesn't fix potential occurrences of function definitions which
are indented (e.g. for a helper class defined in a .cpp), but it's
better than nothing. Also can't be made to run easily on CI/hooks so
we'll have to be careful with new code.
Part of #33027.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Which means that reduz' beloved style which we all became used to
will now be changed automatically to remove the first empty line.
This makes us lean closer to 1TBS (the one true brace style) instead
of hybridating it with some Allman-inspired spacing.
There's still the case of braces around single-statement blocks that
needs to be addressed (but clang-format can't help with that, but
clang-tidy may if we agree about it).
Part of #33027.
|
| |\ \ \
| |/ /
|/| | |
set parser error when infer type is null
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
shadowed var warning in nested block bug fix
|
| | |/ /
| | |
| | |
| | | |
Fix: #38552
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
ThakeeNathees/range-crash-with-non-numeric-const-fix
range() with non-numeric const argument crash fix
|
| | |/ / |
|
| |\ \ \
| | | |
| | | | |
regression: var declaration type info parser bug fix
|
| | | | | |
|
| |/ / / |
|
| | | |
| | |
| | |
| | | |
Part of #33027.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Part of #33027, also discussed in #29848.
Enforcing the use of brackets even on single line statements would be
preferred, but `clang-format` doesn't have this functionality yet.
|
| |\ \ \
| | | |
| | | | |
Allow using integer vectors for iteration and make range() use them
|
| | | | |
| | | |
| | | |
| | | | |
A minor bugfix
|
| | | | | |
|
| | |/ /
|/| | |
|
| |\ \ \
| | | |
| | | | |
GDScript class var type resolve bug fixed
|
| | | | |
| | | |
| | | |
| | | | |
Fix: #37545
|
| |\ \ \ \
| |_|/ /
|/| | | |
parser error for static func access non-static variables
|
| | | | |
| | | |
| | | |
| | | | |
Fix: #38408
|
| |\ \ \ \
| | | | |
| | | | | |
Improved go-to definition (Ctrl + Click)
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Co-Authored-By: Bojidar Marinov <bojidar.marinov.bg@gmail.com>
|
| | |/ / /
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Calling _reduce_node_type from GDScriptParser::_parse_block for assert
was using a current class with a scope that didn't include all
functions. Now calling in GDScriptParser::_check_block_types uses the
right class type. We also now check the assert node message. The assert
line was added to the set_errors associated with assert, since before
the error would be reported on the next line
|
| |\ \ \ \
| | | | |
| | | | | |
Fix: export var type reduce() implemented
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Mark assert lines as safe in gdscript
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now calling _reduce_node_type with debugging enabled to determine
if assert line is safe. Part of doing this required the assert line
to be stored away. Now the AssertNode line is being correctly set.
Newlines are now marked safe always
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
autocomplete for load() function implemented
|
| | |/ / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
GDScript: Fix type inference for const reference to global class
|
| | | |_|/ /
| |/| | |
| | | | |
| | | | | |
Fixes #37529.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Fix unassigned variable warnings for match bindings
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes #34697
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
GDScript class name existance check enhanced
|
| | | |_|_|/ /
| |/| | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Line marked unsafe when base known and index unkonwn
|
| | |/ / / / / |
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | | |
Subgroups were added in #37678 but not properly handled everywhere
where PROPERTY_USAGE_GROUP is.
|
| |\ \ \ \ \
| |_|/ / /
|/| | | | |
`:=` fails on some nodes fix: #37357
|
| | | |/ /
| |/| | |
|
| | |/ /
|/| | |
|
| |/ / |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For us, it practically only changes the fact that `A<A<int>>` is now
used instead of the C++03 compatible `A<A<int> >`.
Note: clang-format 10+ changed the `Standard` arguments to fully
specified `c++11`, `c++14`, etc. versions, but we can't use `c++17`
now if we want to preserve compatibility with clang-format 8 and 9.
`Cpp11` is still supported as deprecated alias for `Latest`.
|
| | |
| |
| | |
Found via `codespell`
|
| |\ \
| | |
| | | |
GDScript duplicate arguments bug fixed
|
