Matthew Flatt

> I think the right choice is probably use emoji rendering when U+FE0F is omitted after a non-Latin-1 character. No, that doesn't seem right after all. It uses emoji rendering...

Properties like `Extended_Pictographic` are on code points, not sequences, right? > Could it be that for unqualified, Firefox tries the "text style" first? Yes, I think selection in many applications...

It's rare for packages to be accessed via HTTP, because most are on GitHub, and the package manager rewrites `http://` GitHub paths to use the Git protocol over SSL. Aside...

The issue isn't `prop:equal+hash` exactly, but the way that `#:methods gen:equal+hash` expands — plus limitations in schemfiy. For example, there's no slow down with ``` (struct foo (bar baz) #:property...

One of the choices in an overall syntax is how to handle grouping. Many alternative notations for Lisps involve the same sort of grouping as parentheses, but written some other...

In Elixir, Remix, and Honu, there are a number of syntactic patterns that are effectively built into the reader layer. The reader converts patterns like infix syntax, dot notations, function...

@rmculpepper Great questions. For 1 and 2, I think probably we didn't notice that problem, because we didn't get to a concrete syntax for macro definitions in Honu (so we...

It's great to see a concrete proposal to help discussion! I remain torn between the alternatives of grouping in a binding-insensitive way (e.g., always until a semi-colon, always parentheses, always...

Another brainstorming variant: use separators for grouping — but do that always, so there's no dependence on binding to group terms. https://gist.github.com/mflatt/f7313e1561210be56313903fd75c6607 As you'll immediately notice, this direction seems to...

Part of this experiment was imagining a distinction between "statement" grouping an "expression" grouping. I had in mind leaving `.` as an expression-level operator like `+` and `*` and `&&`....