favonia
favonia
Proposal @jonsterling @ecavallo - A named variable `a` is printed as the first available in `a`, `a₁`, ..., `a₉`, `a₁₀`... - A named variable `a₂` is printed as the first...
@jonsterling For now, I have to simplify the scheme to: - A named variable `a` is printed as the first available in `a`, `a₁`, ..., `a₉`, `a₁₀`... - An unnamed...
@jonsterling Another subtlety is that we should also avoid shadowing names in the global signature (names of datatypes, constructors, etc).
Yet another option: the removal of inconsistent faces.
After RedPRL/redtt#270.
Updates: We do support options, but the current code structure can be improved. In my opinion, we should replace the ad hoc option setting with reactive programming.
The general design issue I see is to use algebraic effects to communicate such preferences.
Ideally, the module containing the "pure" scopes should be called "Scope", and the module implementing lexical scoping should be called "Scoping". But the latter is taking the name "Scope" now....
@mikeshulman Thanks for the wake-up call. I was expecting "next month (Feb)" but something personal is dragging me all along. My personal issues are still not resolved but I should...
@mikeshulman Hi, I'm getting back on track, and here's one question when I was trying to pin down the API: The `Scope` module actually uses more than the scoping effects....