The serde_path_to_error deserializer wrapper provides much more useful deserialization errors than serde's standard error messages. We should consider using it throughout the driver wherever we perform deserialization. We should also benchmark to make sure using this wrapper isn't a performance/memory usage hit. If it does make an impact, we could consider adding a feature flag for it. We've had many user complaints about serde's lack of detail in deserialization errors, so users might still want to use this wrapper even if it comes with a penalty.