Jacques Carette

The conclusions in the last post above (about `VisibiliySym` and `ScopeSym` make sense. We do want script-like programs with global variables as well as proper programs (and libraries) that don't....

The problem is that `pair2` wants to create a function of 2 *state* arguments from functions with 2 arguments each. Basically: I don't think this is the right combinator to...

If we want "scope-polymorphic variables" (for their convenience) then I think we should introduce 'pre-variables' for that purpose. These would need to have their scope specified 'later' when they are...

Scripts and functions and loops should know what scope they need their variables to be, so they should control the scope. I was originally thinking that they would choose between...

Is this issue still 'live'? It feels like there has been some progress on it.

See my comment on #3888 . The idea is right, but since everything is in the `State` monad already, we should use that instead of explicitly weaving things around.

Eventually, what we'll probably want is for both `drasil-code` and `drasil-gool` to keep track of the current scope *and* tag each variable with the scope it belongs to. Having more...

Amusingly, this is somewhere we could use Haskell's laziness to our advantage: we could lazily generate names and only force them to be actually generated once the full block of...

In theory, nothing to do. In practice, you need to make sure you're not doing certain pattern matches "too early" as that will force evaluation. Plus someone's work (Noah?) on...

The change should go even further up: `Figure` as defined in `drasil-lang` (i.e. in `Language.Drasil.Document.Core`) should already have the information in it whether there is a caption or not. Might...