Library cannot use named functions for values

[ssoelvsten]

Consider the following (minimised) version of the unit testing library I've been writing

(** FILE: lib/Unit.trp *)
let
    (*--- Pretty Printing ---*)
    fun yellow s = "\x1b[33m" ^ s ^ "\x1b[0m"
    val testStr = yellow "[ TEST ] "

    (*--- Test Creation ---*)
    fun foo _ = 42

    (*--- Module ---*)
    val Unit = {
        foo    = foo
    }
in [ ("Unit", Unit) ]
end

imported as follows

(** FILE: test/lib/Unit.trp *)
import Unit

let val _ = Unit.foo
in 0
end

At runtime, the import breaks with the following error

file:///troupe/rt/built/loadLibsAsync.mjs:41
        let table = libinstance.export({ __dataLevel: levels.BOT }).val.toArray();
                                                                       ^

TypeError: Cannot read properties of undefined (reading 'toArray')
    at loadLibsAsync (file:///home/soelvsten/git/postdoc/troupe/rt/built/loadLibsAsync.mjs:41:72)
    at async UserRuntimeZero.linkLibs (file:///home/soelvsten/git/postdoc/troupe/rt/built/builtins/UserRuntimeZero.mjs:228:9)
    at async start (file:///home/soelvsten/git/postdoc/troupe/rt/built/runtimeMonitored.mjs:397:5)

As far as we can tell, the library is compiled into a closure rather than as a list exported values.

[ssoelvsten]

Slightly related might also be that printing \r does not seem to actually reset the carriage such that you can overwrite the output.

[AStenbaek]

Slightly related might also be that printing \r does not seem to actually reset the carriage such that you can overwrite the output.

Do we know if this stems from the runtime library handling printing, or is it something happening in the compiler? If the former, this is would be a separate issue.

I recall I had an issue with printed >>> (colored green) in my calculator example being turned into > (without color), if I ever deleted a character in the terminal.

[ssoelvsten]

Andreas' and I minimised the example to the following: a named function is used to derive a val.

(** FILE: lib/fail.trp *)
let fun i x = x
    val i2 = i 2
in [ ("i2", i2) ]
end

with the test case

(** FILE: run_fail.trp *)
import fail
i2

In this case, it moves the final export creation into a continuation which is put on the stack but not returned nor evaluated. Instead, it returns some value - usually a named function.

[ssoelvsten]

The issue seems to be that library import assumes there is no need to actually run continuations/the stack machine.

[ssoelvsten]

With the new module system, we'll allow modules to run initialisation code. But, said code should (like the handlers) be run such that it cannot have any side-effects. This covers all of the use-cases identified in #54 .