Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-05-15 | break, continue outside of a loop, match statement handled | Thakee Nathees | |
2020-05-14 | Merge pull request #38738 from akien-mga/cause-we-never-go-out-of-style | Rémi Verschelde | |
Style: Remove new line at block start, enforce line between functions, enforce braces in if and loop blocks | |||
2020-05-14 | Style: Enforce braces around if blocks and loops | Rémi Verschelde | |
Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html | |||
2020-05-14 | Merge pull request #38610 from ThakeeNathees/infer-type-null-error | Rémi Verschelde | |
set parser error when infer type is null | |||
2020-05-14 | Style: Enforce separation line between function definitions | Rémi Verschelde | |
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. | |||
2020-05-14 | Style: clang-format: Disable KeepEmptyLinesAtTheStartOfBlocks | Rémi Verschelde | |
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. | |||
2020-05-14 | Merge pull request #38611 from ThakeeNathees/shadow-var-warning-bug-fix | Rémi Verschelde | |
shadowed var warning in nested block bug fix | |||
2020-05-13 | set parser error when infer type is null | Thakee Nathees | |
2020-05-13 | Merge pull request #38609 from ↵ | Rémi Verschelde | |
ThakeeNathees/range-crash-with-non-numeric-const-fix range() with non-numeric const argument crash fix | |||
2020-05-13 | Merge pull request #38708 from ThakeeNathees/init-assign-type-parser-bug-fix | Rémi Verschelde | |
regression: var declaration type info parser bug fix | |||
2020-05-13 | regression: static func can't access const fix | Thakee Nathees | |
2020-05-13 | regression: var declaration type info parser bug fix | Thakee Nathees | |
2020-05-10 | Style: clang-format: Disable AllowShortCaseLabelsOnASingleLine | Rémi Verschelde | |
Part of #33027. | |||
2020-05-10 | Style: clang-format: Disable AllowShortIfStatementsOnASingleLine | Rémi Verschelde | |
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. | |||
2020-05-10 | Merge pull request #37020 from aaronfranke/range | Rémi Verschelde | |
Allow using integer vectors for iteration and make range() use them | |||
2020-05-10 | shadowed var warning in nested block bug fix | Thakee Nathees | |
Fix: #38552 | |||
2020-05-10 | range() with non-numeric const argument crash fix | Thakee Nathees | |
2020-05-10 | more clearer unexpected statement end error messages | Thakee Nathees | |
2020-05-09 | Merge pull request #37598 from ThakeeNathees/GDScript-type-resolve-bug-fix | Rémi Verschelde | |
GDScript class var type resolve bug fixed | |||
2020-05-09 | Merge pull request #38412 from ThakeeNathees/static-func-var-access | Rémi Verschelde | |
parser error for static func access non-static variables | |||
2020-05-09 | Change get_completion_identifier_is_function to return a bool | Aaron Franke | |
A minor bugfix | |||
2020-05-09 | Allow using integer vectors for iteration and make range() use them | Aaron Franke | |
2020-05-05 | Merge pull request #37293 from Janglee123/ctrl-click-improvements | Rémi Verschelde | |
Improved go-to definition (Ctrl + Click) | |||
2020-05-05 | Improved go-to definition (Ctrl + Click) | janglee | |
Co-Authored-By: Bojidar Marinov <bojidar.marinov.bg@gmail.com> | |||
2020-05-03 | parser error for static func access non-static variables | Thakee Nathees | |
Fix: #38408 | |||
2020-05-02 | Mention offending function name in "Indented block expected" error | Steven Schoen | |
2020-04-27 | Fix for marking assert lines as safe bug | Tom Evans | |
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 | |||
2020-04-27 | Merge pull request #36927 from ThakeeNathees/export-var-type-reduce-implimented | Rémi Verschelde | |
Fix: export var type reduce() implemented | |||
2020-04-27 | export var type reduce() implemented | Thakee Nathees | |
2020-04-24 | Merge pull request #37265 from BigRed-118/mark_assert_safe | Rémi Verschelde | |
Mark assert lines as safe in gdscript | |||
2020-04-24 | Merge pull request #37232 from ThakeeNathees/load()-autocomplete-imlpemented | Rémi Verschelde | |
autocomplete for load() function implemented | |||
2020-04-21 | Merge pull request #37537 from ThakeeNathees/const-parsing-datatype-bug-fix | Rémi Verschelde | |
GDScript: Fix type inference for const reference to global class | |||
2020-04-21 | Merge pull request #37712 from stoofin/pattern-bind-warning | Rémi Verschelde | |
Fix unassigned variable warnings for match bindings | |||
2020-04-21 | Merge pull request #38041 from ThakeeNathees/class-name-check-enhance | Rémi Verschelde | |
GDScript class name existance check enhanced | |||
2020-04-21 | Merge pull request #37955 from ThakeeNathees/lin-unsafe-base-know-index-unkonwn | Rémi Verschelde | |
Line marked unsafe when base known and index unkonwn | |||
2020-04-20 | Fix handling of PROPERTY_USAGE_SUBGROUP in DocData and editor | Rémi Verschelde | |
Subgroups were added in #37678 but not properly handled everywhere where PROPERTY_USAGE_GROUP is. | |||
2020-04-20 | GDScript class name existance check enhanced | Thakee Nathees | |
2020-04-17 | line unsafe for indexing with known base type & unkown identifier | Thakee Nathees | |
2020-04-10 | Merge pull request #37395 from ThakeeNathees/collon-equal-parser-bug-fix | Rémi Verschelde | |
`:=` fails on some nodes fix: #37357 | |||
2020-04-09 | Pattern bind counts as assignment | Stoofin | |
Fixes #34697 | |||
2020-04-05 | GDScript class var type resolve bug fixed | Thakee Nathees | |
Fix: #37545 | |||
2020-04-03 | GDScript: Fix type inference for const reference to global class | Thakee Nathees | |
Fixes #37529. | |||
2020-04-02 | Replace NULL with nullptr | lupoDharkael | |
2020-03-29 | `:=` fails on some nodes fix: #37357 | Thakee Nathees | |
2020-03-28 | Fix for loop range bug: #37358 | Thakee Nathees | |
2020-03-25 | Mark assert lines as safe in gdscript | Tom Evans | |
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 | |||
2020-03-22 | autocomplete for load() function implemented | Thakee Nathees | |
2020-03-17 | Style: Set clang-format Standard to Cpp11 | Rémi Verschelde | |
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`. | |||
2020-03-11 | Fix various typos | luz.paz | |
Found via `codespell` | |||
2020-03-10 | Merge pull request #36704 from ThakeeNathees/gdscript-duplicate-args-fix | Rémi Verschelde | |
GDScript duplicate arguments bug fixed |