Confusion about package import limitations

[timothytmzhou]

Hello,

I have some confusion about the following line in the limitations section of the README:

Importing a module from the current package is not supported. It might look like it works on one day and then segfault the next day. You have been warned.

This is probably a dumb question, but I don't understand what "importing a module from the current package" means. Specifically, when I look on the stackage documentation for loadModules, I see this:

In particular, you need to avoid modules that define types that will later occur in an expression that you will want to interpret.
The problem in doing this is that those types will have two incompatible representations at runtime: 1) the one in the compiled code and 2) the one in the interpreted code. When interpreting such an expression (bringing it to program-code) you will likely get a segmentation fault, since the latter representation will be used where the program assumes the former.

My understanding from reading this is that the problem is specifically with loadModules, not setImports. In particular, if I never call loadModules will such issues be avoided entirely? More concretely: if a package P contains code that uses hint, and that code calls setImports on a module from P but never calls loadModules, is that still unsafe?

Thanks!