Aleksander Sabak
Aleksander Sabak
I have left out one possible expected outcome: that both output `t` because the compiler should optimize creation of slotless tuples, but I will argue that for this use case...
So if this only occurs in the listener then does it mean that the *non-optimizing* compiler is the one behaving incorrectly?
This PR seems to completely break `read-contents` on the `interactor`, which in all fairness makes it somewhat consistent with the cli listener. It doesn't react to the enter key alone...