Previously this argument passed multiple times would result in the first
being silently ignored.
Details
- Reviewers
jansvoboda11
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Event Timeline
There are many options whether the latter one overrides the previous ones. How is this special?
Fair question! I think this case is a bit different since it's quite subtle. The strange thing here is that the header you're intending to provide a pch for can still be read successfully, but not getting the benefits of the pch that you were expecting without knowing about it.
Is there any reason that -include-pch shouldn't follow the precedent of -include, which can be used multiple times? If not, then the end goal should be to support multiple uses, but in the mean time a warning is helpful.
Yea seems like a reasonable request, looking through the uses nothing immediately pops out as being not supporting multiple PCHs but I guess before I went down that path I'd want someone who knew the code better to agree on that