Mitchell Dalvi Rosen

I experimented a bit and determined the mere existence of unfinalized statements actually doesn't make `VACUUM` fail.

This was regarded as "actually a feature" as of Dec. 2020, but not with strong feelings in either direction: https://github.com/unisonweb/unison/issues/1776

Share does load all names in order to construct the pretty-print environment.

@pchiusano Interesting.I think they do cover different enough use cases for both of them to potentially be important. Archived namespaces wouldn't help load an Ed Kmett root with dozens of...

`generic-lens` is like `has`++ ;) ```haskell type MyEnv = (Fooby, Barby, Bizzy) whop :: RIO MyEnv Response whop = do fooby

Oh, and another reason to prefer backpack: it cleans up type signatures a lot :) Compare: ```haskell -- typeclass newScope :: MonadConc m => m (TMVar (STM m) (Scope m))...

> Is there a good primer on backpack somewhere? I don't there's a great, concise primer. I found this wiki page which contains all the info you need, scattered about...

I assume you'd (always?) rather run `./file` when `file` is touched, in case `.` is not in your PATH.

I'm slightly in favor, as you're right it doesn't clash with any syntax. Currently, running `sos` without any `-c` arguments (and no yaml file) is basically a mistake :)

If process A (steeloverseer) runs command B (cabal run) which itself spawns something (C) and then exits, C becomes a zombie. In this case it's B's job to wait on...