Andy Wingo <wi...@igalia.com> writes: > On Mon 09 Nov 2015 08:51, taylanbayi...@gmail.com (Taylan Ulrich > "Bayırlı/Kammer") writes: > >> The relevant bug report is <http://bugs.gnu.org/15602>. >> >> According to Ludo's explanation, compiling a module file leads to the >> module being created in the runtime, but with syntax bindings only, and >> runtime bindings missing. That's what I mean with "degenerate" module >> for lack of a better term. Loading the same file explicitly afterwards >> (or using load-compiled on the generated .go) seems to solve the issue. > > Ah, I see. Well, one workaround for this issue, if you wanted to work > around it, would be to load the file before compiling it. In that way > the module would already be loaded at the right phase. This wouldn't > cost very much AFAIU.
Yeah, loading before compiling also seems to work. Neither solves the other error I got, so I guess that one is really unrelated to this. I'm still clueless on that one. Taylan
