Commit: b78b6e3cd71b15ca2c8ab32717d91102c5915352 Author: Hans Goudey Date: Wed Nov 30 11:49:32 2022 -0600 Branches: master https://developer.blender.org/rBb78b6e3cd71b15ca2c8ab32717d91102c5915352
Cleanup: Correct comment in hash description We use the blender namespace now rather than BLI. =================================================================== M source/blender/blenlib/BLI_hash.hh =================================================================== diff --git a/source/blender/blenlib/BLI_hash.hh b/source/blender/blenlib/BLI_hash.hh index c29dc74599a..1c9dd3914cf 100644 --- a/source/blender/blenlib/BLI_hash.hh +++ b/source/blender/blenlib/BLI_hash.hh @@ -33,14 +33,14 @@ * * There are three main ways to provide a hash table implementation with a custom hash function. * - * - When you want to provide a default hash function for your own custom type: Add a `hash` + * - When you want to provide a default hash function for your own custom type: Add a `hash()` * member function to it. The function should return `uint64_t` and take no arguments. This * method will be called by the default implementation of #DefaultHash. It will automatically be * used by hash table implementations. * * - When you want to provide a default hash function for a type that you cannot modify: Add a new * specialization to the #DefaultHash struct. This can be done by writing code like below in - * either global or BLI namespace. + * either global or `blender` namespace. * * template<> struct blender::DefaultHash<TheType> { * uint64_t operator()(const TheType &value) const { _______________________________________________ Bf-blender-cvs mailing list Bf-blender-cvs@blender.org List details, subscription details or unsubscribe: https://lists.blender.org/mailman/listinfo/bf-blender-cvs