Corbin Simpson

We had a chat on IRC. We'll need to talk more later.

Another problem: Objects like `Int` don't actually implement the `Interface` interface! This is the cause of this annoying bug: ``` ▲> help(42) TRACE: ["In To obtain help on an object,...

As of 04c0b70b4201860c634ccce21a7a32766d5f2914, `Int` and friends now have automatically-generated correct interface methods.

We need to figure out the right story for the builtin objects using non-generated interfaces. Should we just stop doing that?

Named params were added to interfaces in b3d901e.

Imagine a submarine near the bottom of the ocean. It must ping the ocean floor in order to see its surroundings, but the surroundings are largely persistent between pings, so...

Opinion! The named arguments of `traceln()` are collected, Miranda arguments discarded, and the rest tossed into a structure. Trace logs become rows of structured events, with a list of arguments...

This was an excellent IRC discussion. I agree. Of the suggestions, I like `M.now()` the best. It would presumably carry a POSIX UTC timestamp, in seconds, as a Double. Or...

I often would just like to have `.fetch/1`; I want a default value predefined. This bit me yet again today.

The index is picked based upon this function: def cut(l, i) { return [l.slice(0, i), l.slice(i, l.size())] } And it has the same behavior: ▲> cut([1, 2, 3, 4], 2)...