Skip to content
This repository has been archived by the owner on Mar 24, 2022. It is now read-only.

Ensure the pretty-printed versions of errors are as we expect across all the crates #409

Open
acfoltzer opened this issue Jan 31, 2020 · 0 comments

Comments

@acfoltzer
Copy link
Contributor

#408 solved the immediate problem of lucetc not offering useful error messages, but there are other crates that likely need the same treatment. We also should make error messages part of our test suite, at the very least doing things like ensuring the missing symbol appears in the message for a bad binding.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant