@roadriverrail Yeah, I've definitely see my fair share of "Our standard library interface simplifies a common (for us) use case. If you want to do things that are technically allowed by the relevant protocols but don't fit our use case then go rummage in our code and start inheriting and overriding undocumented internals that may change next release (next week). Or stop doing standard stuff that's outside our implied common use case."