waynr commented on issue #7171: URL: https://github.com/apache/arrow-rs/issues/7171#issuecomment-2675466557
Just some questions since I'm still fairly green when it comes to really understanding the intricacies of Rust's type system... > As a wrapper must avoid "despecializing" methods, it must implement all 18 methods I'm not sure what you mean when you say that wrappers must avoid de-specializing. Does that have something to do with compiler optimizations? > Encourage use of specialized traits like parquet's AsyncFileReader that reflect what a given component actually needs, and can evolve independently of ObjectStore So this would also involve using something like the `ParquetFileReaderFactory`, right? And that's the level at which, in the case of a caching implementation that I described in #7135 and #7155, I would need to have session state/config information available to pass to a custom implementation to get properly-parented spans? It looks like this and related interfaces don't currently support accepting opaque contextual data but maybe you're suggesting they are more open to that kind of change than `ObjectStore`? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
