...1
This removes a source of grammatical complexity in a language where anyone can add new binary selectors or implementations. It is our policy that conventional mathematical notation and visual convenience belong in user interface libraries.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...thisContext x: 4.2
The current named method as distinct from the context is available as currentMethod, and its name is available as selector. However, these are dependent on the current implementation of Slate, and so may not be available in the future.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...P3
We may also provide these as `up and `down, respectively, if there is enough demand for it, and it is not too confusing.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...4
Future, bootstrapped releases may provide for partitioning of the global table.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... automatically5
However, support for blocks in the second argument position may be incorporated into the non-lazy selectors as different methods in the future, making some of these obsolete.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...6
In the future, automatic querying and loading an appropriate module could be added.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.