Anonymous user
User:Colby Russell/Composability: Difference between revisions
punctuation
(details of a third composability problem) |
(punctuation) |
||
| (One intermediate revision by the same user not shown) | |||
Line 1:
There are two areas we have unsolved composability concerns in the triple scripts ecosystem:
* when a general purpose libpack that we link against is itself a valid triple script (we need to transform its shunting block; maybe this should be as simple as truncating the IIFE with a semicolon—replacing the invocation parens XXX 2023 March: Replacing the parens can be a problem for roundtripping, so consider instead a scheme whereby we (a) insert the semicolon as described, and (b) insert the token <code>`inert`</code> immediately after the IIFE open paren—we need only delete those two tokens, which is "safer" than remove-and-resynthesize XXX when looking for these tokens, should the token stream be whitespace-sensitive? A: Probably; reject any inputs that don't match exactly the sort of output that the compiler produces.)
* distinct from the case of linking against an existing program for use as a lib, we want to be able to more-or-less contrive of a format that allows us to chain multiple programs together in a "pipe"
| |||