Skip to content

ugly error message #815

New issue

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

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

Already on GitHub? # to your account

Closed
shriram opened this issue Aug 2, 2016 · 2 comments
Closed

ugly error message #815

shriram opened this issue Aug 2, 2016 · 2 comments

Comments

@shriram
Copy link
Member

shriram commented Aug 2, 2016

> r1 :: Reactor = r
Name not found in globals.types: Reactor"

"globals.types" should never be seen from the outside.

@jpolitz
Copy link
Member

jpolitz commented Aug 2, 2016

Thanks, that's because of a silly bug where the type environment and modules had a gap in agreeing on names.

This is mostly fixed by 88732aa, but @mkolosick, it is another place where the type checker now will be confused about type aliases vs. datatypes, so will need to iron that out. (Currently, this makes the type checker look for an alias that isn't there, while the dynamic namespace works fine).

@sorawee
Copy link
Contributor

sorawee commented Sep 17, 2017

@jpolitz it doesn't seem to be fixed. I still see same error message. See also #1013

jpolitz added a commit that referenced this issue Jul 30, 2019
…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>
jpolitz added a commit that referenced this issue Aug 26, 2019
…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>
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

4 participants