John Fairhurst

Great. I'm going to keep this around while SwiftPM decide whether they have a bug or not.

This is a Swift bug, it's wrong coming out of SourceKit. Latest swift/master: ```shell ; cat Test.swift struct gg {} ; sourcekitd-test -req structure Test.swift { key.request: source.request.configuration.global, key.optimize_for_ide: 1...

If you still have this problem on the latest version then we'll need a sample project to investigate: nothing is out of the ordinary in the setup you've described.

Unexpected struggle getting this to work: Xcode 15.3 has an undocumented feature in `xcodebuild` and other places where environment variables from the invoking environment are discarded. This includes `DEVELOPER_DIR`. So...

Longer than I meant to take getting back to this. Apple has [confirmed](https://forums.developer.apple.com/forums/thread/749185) that this env. var thing is working as designed -- sounds like the alternative to `xcode-select` is...

This looks like a good idea, have had a few jazzy users wanting this kind of thing. Could do with some unit tests for those extensions. `NSPredicate` is [incomplete on...

Just what the message says really: it means Swift thinks that the source file you are querying (`key.sourcefile`) does not appear in the list of files passed to the compiler...

No, nothing at all to do with "the parsing process", it's about the keys in your sourcekit request per my previous comment.

The compiler args are supplied by the user or taken from the build tool CLI/record. If you are not making sourcekit requests directly, can you explain exactly which sourcekitten interface...

None of that sends a cursorInfo request. If you have a source file that causes the cursorInfo error from the OP when you run that `Structure` query (sends `source.request.editor.open`) then...