chaokunyang commented on issue #2595: URL: https://github.com/apache/fory/issues/2595#issuecomment-3271250802
Some things needs be done: - [ ] Make arrow integration optional, not all users needs this integration - [ ] Make fory cpp reflection system decoupled from arrow type system - [ ] Add cmake build support, since most cpp users use cmake for build - [ ] Add type resolver for object graph in c++ - [ ] Add reference resolver for object graph in c++ - [ ] Build a macro/template based compile-codegen system for fory-cpp. Note that fory cpp use c++ 17, and we won't use c++ 20. Build compile-reflection systemm may take some efforts. - [ ] Support serialization for basic types - [ ] Support serialization for nested collection/map/set types using compile-codegen module - [ ] Support serialization for struct and nested struct using compile-codegen module - [ ] Support type meta encoding for schema evolution - [ ] Support schema evolution serialization based on type meta, we need to generate two version of deserializaion code at compile-time - [ ] Support circular and shared reference such as shared_ptr, weak_ptr, unique_ptr -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
