maltzsama commented on issue #96: URL: https://github.com/apache/arrow-swift/issues/96#issuecomment-5164688115
Yes @willtemperley , AI-assisted. You're right that the executable takes arbitrary paths, that removes the dependency I claimed. And the XCTest in #185 does duplicate what Archery would cover; it's a draft so I'll strip it back rather than build on it. What I want to get right is the order. Two questions: **First PR.** `arrow-file-to-stream` / `arrow-stream-to-file` need no JSON handling at all, so they're the smallest thing that gets an executable target in place. Useful starting point, or not worth a PR on its own and the JSON reader should come first even though it's bigger? **Types vs. plumbing.** Most of the corpus doesn't read today, decimal, dictionary, union, map, interval, null, the view types all fail on `unknownType`. So a first pass at Archery would skip most cases. Is landing that with a long skip list the right move, or would you rather see types implemented first so the integration starts out meaningful? -- 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]
