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

Using a package before it is #require'd will result in unbound module errors even after it is later #require'd. #54

Open
ciaran16 opened this issue Jul 13, 2016 · 1 comment

Comments

@ciaran16
Copy link

For example, Core.Std.printf "Hello world" results in Error: Unbound module Core as expected. However if I then do #require "core.top" and then rerun the above, I still get Unbound module Core.

If I restart iocaml and make sure to #require a package first, then it works fine.

@andrewray
Copy link
Owner

That is something I have seen before. There was some logic I didn't get working (related to something like Btype.snap or somesuch) which might be related.

FWIW rather than restart iocaml, you can just restart the kernel with 'ctrl+m .'

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

No branches or pull requests

2 participants