> So are we moving toward:
>
> ___ __* __= __1 object $ struct get! ***
>
> along with
>
> = and or set! not

Please keep in mind that with many fonts, identifiers that have more
than one consecutive underscore are really hard to read since the
underscores get welded into one another with no gaps in between. It's
hard to notice whether something has 2 or 3 underscores.

This is a particular concern given Scheme's lack of type checking. If 3
underscores is a special identifier but 2 is a normal variable name,
it's easy to cause bugs.