Don't return reference on copy assignment operators
We prefer to prevent using chained assignment (`T a = b = c = T();`) as this can lead to confusing code and subtle bugs. According to https://en.wikipedia.org/wiki/Assignment_operator_(C%2B%2B), C++ allows any arbitrary return type, so this is standard compliant. This could be re-assessed if/when we have an actual need for a behavior more akin to that of the C++ STL, for now this PR simply changes a handful of cases which were inconsistent with the rest of the codebase (`void` return type was already the most common case prior to this commit).
This commit is contained in:
parent
2d118bd8b8
commit
7da392bcc5
28 changed files with 93 additions and 90 deletions
|
|
@ -488,8 +488,8 @@ void EditorExportPlatform::_edit_files_with_filter(DirAccess *da, const Vector<S
|
|||
String cur_dir_no_prefix = cur_dir.replace("res://", "");
|
||||
|
||||
Vector<String> dirs;
|
||||
String f;
|
||||
while ((f = da->get_next()) != "") {
|
||||
String f = da->get_next();
|
||||
while (!f.is_empty()) {
|
||||
if (da->current_is_dir()) {
|
||||
dirs.push_back(f);
|
||||
} else {
|
||||
|
|
@ -506,6 +506,7 @@ void EditorExportPlatform::_edit_files_with_filter(DirAccess *da, const Vector<S
|
|||
}
|
||||
}
|
||||
}
|
||||
f = da->get_next();
|
||||
}
|
||||
|
||||
da->list_dir_end();
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue