Oran Agra

ok. so let's do what we think is right. @hwware wanna refresh this PR and decide which of the unlisted commands should be listed and which ones can be skipped?

@weim0000 have you really reproduced this? can you share the reproduction scenario? or is it just a theoretical issue from reviewing the code. @madolson please take a look.

@ranshid thanks (it'll take some time till i'll get to review this). for the record, i do support renaming `bpop`, i think it's about time..

@ranshid i don't understand why a merge commit would be a problem. i'd prefer you avoid that next time. anyway, water under the bridge now, so please tell me which...

@ranshid the other PR was merged, please merge unstable into this one, p.s. discussed it and conceptually approved it in a core-team meeting.

@redis/core-team please approve, adds a "display" field for command arguments in COMMAND DOCS output. more details at the top.

@guybe7 please make a PR to update the docs of COMMAND DOCS, and also coordinate with @itamarhaber what should be done in order for redis.io to render the new display_text...

for the record, i'm not sure the absolute worse case, and the reasonable one are so far apart. it could be that the object has one big field, and another...

some things i'm not sure i understand: * why do you sum the extra pointer in hashDictType / setDictType / zsetDictType? it's one instance per server (not per key) *...

@filipecosta90 #10697 does exist in v7.0.3. at the time 7.0.3 was release, everything in unstable was included in it.