Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wording change for unknown explicit import #1232

Closed
hdgarrood opened this issue Jul 5, 2015 · 2 comments
Closed

Wording change for unknown explicit import #1232

hdgarrood opened this issue Jul 5, 2015 · 2 comments

Comments

@hdgarrood
Copy link
Contributor

For example:

module Main where

import Prelude (thisDoesNotExist)

currently gives "Unknown value Prelude.thisDoesNotExist". I think "Prelude does not export thisDoesNotExist" would be better, in order to help differentiate it from, eg, errors arising from values not being in scope in expressions.

@puffnfresh
Copy link
Contributor

👍

1 similar comment
@paf31
Copy link
Contributor

paf31 commented Jul 6, 2015

👍

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

No branches or pull requests

4 participants