tutorials/best_practices/data_preferences

[giscus[bot]]

tutorials/best_practices/data_preferences

Ever wondered whether one should approach problem X with data structure Y or Z? This article covers a variety of topics related to these dilemmas. Array vs. Dictionary vs. Object: Godot stores all ...

https://docs.godotengine.org/en/stable/tutorials/best_practices/data_preferences.html

[sebbasim]

Enumerations: int vs. string
If I understand correctly, if you use @export_enum, you lose type checking. This is an important consideration, and should be included in the paragraph.

[Clark-E]

The details about how Dictionaries are implemented seem to be incorrect or outdated. Unless I'm mistaken, Dictionaries sizes aren't powers of 2, but instead use the sizes defined by hash_table_size_primes in core\templates\hashfuncs.h. Also, Dictionaries don't use OrderedHashMap (which isn't in the codebase,) but instead use HashMap<Variant, Variant, VariantHasher, StringLikeVariantComparator>.

[Phanterm]

It is worth mentioning that one can access an existing function on named enums by calling MyEnum.keys()[], passing into the brackets the value of any property using this enum. One need not write their own Dictionary for this as is stated on this page. For example:

enum RiceType {
    Jasmine,
    Basmati,
    Calrose
}

var favorite_rice : RiceType = RiceType.Jasmine

print(favorite_rice)

Because favorite_rice = RiceType.Jasmine, this line will print 0, as Jasmine occupies index 0 of our RiceType enum.

print(RiceType.keys()[favorite_rice])

This line will print Jasmine. Because we are accessing the Dictionary stored on the RiceType enum, and by passing in favorite_rice (which, remember, is equal to 0 because Jasmine is at index 0), we return the key at that position.