Re: [Interest] QMap<> function documentation

2022-05-28 Thread Thiago Macieira
On Saturday, 28 May 2022 07:31:33 PDT Michael Jackson wrote: > Should I put in a bug report on this so that the docs get updated at some > point in the future? It's already happened. -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering

Re: [Interest] QMap<> function documentation

2022-05-28 Thread Michael Jackson
Should I put in a bug report on this so that the docs get updated at some point in the future? -- Mike Jackson On 5/25/22, 12:51 PM, "Interest on behalf of Thiago Macieira" wrote: On Wednesday, 25 May 2022 09:19:52 PDT Michael Jackson wrote: > Specifically for the part of “value(…)”

Re: [Interest] QMap<> function documentation

2022-05-25 Thread Thiago Macieira
On Wednesday, 25 May 2022 09:19:52 PDT Michael Jackson wrote: > Specifically for the part of “value(…)” and “values(…)” that talk about > “multiple values for a key”. Each key is unique in the QMap so how would I > have multiple values associated with a key? Maybe I’m just not > understanding what

[Interest] QMap<> function documentation

2022-05-25 Thread Michael Jackson
I feel like the documentation for QMap<>::value and QMap<>::values is a bit misleading: const T QMap::value(const Key &key, const T &defaultValue = T()) const Returns the value associated with the key key. If the map contains no item with key key, the function returns defaultValue. If no defa