Where possible, I added additional information to the messages to help
programmers figure out what went wrong. I also removed all uses of the word
"bad" from the messages since (to me) that implies a moral judgement rather
than a programming error. I replaced it with either "invalid" or "unsupported"
where appropriate.
Details
Details
- Reviewers
klausler jeanPerier - Commits
- rGe3550f1903d2: [flang] Improve runtime crash messages
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
@klausler, do you also prefer "bad" in all contexts, including for messages related to invalid/unsupported KIND specifications?