... | ... | @@ -491,6 +491,7 @@ mkMsgEnvelope dflags locn print_unqual err |
|
|
```
|
|
|
|
|
|
This appears to be more efficient (we more eagerly drop any ignored messages) but it requires all callers of `mkMsgEnvelope` to deal with the possibility of failure. A quick review of usage sites suggests this won't be hard (the result is often just put into a bag, and if `mkMsgEnvelope` returns `Nothing`, it's very easy to put nothing into a bag), but this design is definitely more invasive than Design A.
|
|
|
|
|
|
</details>
|
|
|
|
|
|
|
... | ... | |