There are some trade-offs on using SourceKitten, including a larger dependency base. In addition, I'm not terrible fond of the API usage, but that's not a terribly big deal.
Three options:
Use SourceKitten as-is
Fork SourceKitten, clean-up the API and implementations, and send PRs
Create a small wrapper over SourceKit itself
I'm leaning towards #2, but need to do some more investigations.
There are some trade-offs on using SourceKitten, including a larger dependency base. In addition, I'm not terrible fond of the API usage, but that's not a terribly big deal.
Three options:
I'm leaning towards #2, but need to do some more investigations.