shot myself by having the CBOR decoder lazily serializing to atproto's lex-json format, in operator is a perf killer and I can't remove it from the encoder side
i certainly don't have to focus on perf any further but it's just nice if it can do it honestly
"hold on, in operator is slow?" it is, that's why there's a check for undefined before checking if the key even exists
@mary_ext What does it do that makes `in` slow anyway?
If input is something like a hash table then it should be just as fast as grabbing the value no?