Add one more point about the benefits of a generic construct
This commit is contained in:
parent
65665926ae
commit
b79d081178
|
@ -170,6 +170,10 @@ rather than a specialized case-insensitive dict variant. The answer
|
|||
is that it's nearly as cheap (code-wise and performance-wise) to provide
|
||||
the generic construct, and it can fill more use cases.
|
||||
|
||||
Even case-insensitive dicts can actually elicit different transformation
|
||||
functions: ``str.lower``, ``str.casefold`` or in some cases ``bytes.lower``
|
||||
when working with text encoded in a ASCII-compatible encoding.
|
||||
|
||||
Other constructor patterns
|
||||
--------------------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue