summaryrefslogtreecommitdiff
path: root/CHANGELOG.md
diff options
context:
space:
mode:
authorreduz <reduzio@gmail.com>2022-02-08 08:55:20 +0100
committerreduz <reduzio@gmail.com>2022-02-08 09:21:10 +0100
commit38232c70db31eaca3ae9ac770b763141d6daa68c (patch)
tree50f81ec8fe11ce6c9bc4bfc136dd03306328f3b5 /CHANGELOG.md
parentd6ba4a223fc394fa2fd9321c19468e05b5de1de0 (diff)
Clarify SNAME usage
* Explain where it should be used, with examples. * Clarify that it should _not_ be used everywhere, only where needed. * Supersedes #57720 This PR is the result of the discussion that happened in a contractor meeting, and it attempts to clarify the intended use for this macro for other contributors. As a personal note, It is my view that other approaches to using SNAME (like having a global or per class table of string names) are mere overengineering without any real benefit (performance remains the same, and usage of stringnames becomes more cumbersome. Additionally, there was not any significant amount of errors in name mismatching as a result of using strings since Godot was open sourced).
Diffstat (limited to 'CHANGELOG.md')
0 files changed, 0 insertions, 0 deletions