Show more useful errors when using invalid compiler arguments
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Swift
- Stars
- 2.4k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
$ echo '/// YOLO\nclass YOLO {}' > yolo.swift
$ sourcekitten doc --single-file yolo.swift yolo.swift
Illegal instruction: 4
$ brew ls sourcekitten
/usr/local/Cellar/sourcekitten/0.3.1/bin/sourcekitten
[...]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the command shown with sourcekitten doc --single-file and the yolo.swift input, then trace how invalid compiler arguments are handled. The issue names no source files or tests, so identify the relevant command entry point and add coverage for the reproduction; done means a useful compiler-argument error is reported instead of an illegal-instruction crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100