morenonicolelli commented on issue #78: URL: https://github.com/apache/arrow-swift/issues/78#issuecomment-3187405574
I read you comment and the page and now I understand what's the purpose of ArrowC and go-swift. In my opinion, instead of remove go-swift, we could integrate it into tests. Starting making a plan: - move all the target in the right folder; (my PR, maybe I'll going to modify something) - test that everything is the same as before, using unit test and external visibility. From outside user can use only Arrow? Or it's reachable also FlightArrow? - check CI/CD pipeline and make it works. - better integration for ArrowC and go-swift into tests. I have to check deeply what I have to do but them are not plugin, just target used for testing. Maybe later we can think better about it; This is my plan to close this issue. Next step is move the package to Swift 6.1 but I read better about it: We have to move carefully because we have to maintain the portability to Swift 5. -- 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
