Hmm. There's no precedent for this, at least as far as `StdioException` goes. The exception is thrown in a dozen places, and none of those convey file/line information, even when that exception is thrown directly. IMHO it's better to fix this all at once separately, but since either way the exception information will always point to somewhere inside Phobos, there really isn't a strong motivation to do that. (The whole deal with passing file/line information across Exception constructors seems like a giant hack around subpar stack traces anyway.)