Anton Dyudin

Yeah, the answer to "what's harder -- implementing a plain text view or straight up fixing the editing experience" when accounting for all possible corner cases is definitely the former....

Huh, if the `Dockerfile` is on iSH, do `COPY` commands resolve against iSH or against the remote host?

Possibly related: `^+ |- ?: %& _@ $ `` crashes only at the pretty-printer, instead of type-failing.

Stretch goals: run the slow code and then switch midair to a fast single-pass inlining output and then if the `Fn`'s still live switch *again* to the output of a...

Is this a `Pin`, or just like, a `Cell`?

> Also we don't have any multi-threading support yet lol. I imagine the `FastFn` is as `Send` and `Sync` as the input closure?

I certainly vote there not be any unprintable(or unparsable) valid `@l` values :\) (Relatedly, do we have nans? negative zero? *probably* reusing all the individual float parsers Just Works here)

> ``` > `@lvs`~ > 0x1 > ._ > ``` This seems not ideal given tuple literal form(e.g. `._1_2_3__`), do we have any other prefix ambiguities?

Do we know the problem with building files at old versions?

…no `%cx` makes clay a non-revision-controlled file system, quite (I guess you can always make a new desk to "tag" a specific case? But interface-wise)