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.

Sign up for GitHub

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

Jump to bottom

Using a built-in module name as a type causes an internal error #1332

Closed
jpolitz opened this issue Apr 6, 2018 · 2 comments
Closed

Using a built-in module name as a type causes an internal error #1332

jpolitz opened this issue Apr 6, 2018 · 2 comments

Comments

@jpolitz
Copy link
Member

jpolitz commented Apr 6, 2018

For example:

a :: option<Number> = some(5)

which is an easy typo of the intended program:

a :: Option<Number> = some(5)
@jpolitz
Copy link
Member Author

jpolitz commented Apr 6, 2018

NB: This is a namespace error, not a type-checker error

@blerner
Copy link
Member

blerner commented Jul 17, 2019

Well it's slightly less bad on the modules branch: "Name not found in globals.types: option"

Still not good, but at least the internal error is avoided

jpolitz added a commit that referenced this issue Aug 26, 2019
@jpolitz @blerner
Refactor compile-module to avoid calculating provides on bogus progra…
f139618 
…ms, which causes exceptions rather than reporting the compile errors

[fixes #1332, fixes #1013, fixes #815]

Co-authored-by: Ben Lerner <blerner@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jpolitz @blerner