This is a work in progress PR to address #17 that marks a major overhaul of SourceKitten focusing on modularity, testability and architecture.
Using dynamic frameworks through Carthage for dependencies and keeping core functionality in SourceKittenFramework should help in the long-term maintainability of this project.
The project structure is heavily inspired by Carthage itself so a HUGE thanks to the people behind that project for their hard work. Shipping command line tools with Swift frameworks is pretty tricky and they've managed to find a decent solution, which I opted to piggy-back on :pig2:.
Steps until we can merge this: - [x] Write comment docs. Current comments are entirely out of date, so please don't pay attention to them. - [x] Write more tests. Especially in SwiftDocsTests, ModuleTests and OffsetMapTests. - [x] Make sure jazzy's integration tests still work and manually test a few other projects. - [x] Make sure sourcekitten will prioritize frameworks in the same directory over the ones in ~/Library/Frameworks. - [x] Reintegrate ObjC/Clang proof-of-concept. - [x] Re-add "parsing File.swift (1/1)" stderr messages. - [x] Print SourceKittenFramework errors. - [x] Find work-around for SourceKit inconsistency issue. - [x] Write proper CHANGELOG entry.
That being said, if you keep in mind that I have yet to complete these steps, I'm very open to review. I'd recommend you mostly ignore the diff and take a more comprehensive look.
该提问来源于开源项目：jpsim/SourceKitten
