Kevin Lawler

``` In k3.2: b:32 There is no display of the value of b in k3.2. In kona: b:32 32 ``` I am fairly sure this could be done easily with...

``` In a fresh session of k3.2, executing the sentence {x}2 does not add x to the K-tree. In kona, it does. ``` This is accurate. I would add that...

Interesting, and good history, I didn't know that.

Pasting some of the older material: ``` it's k3 that's inconsistent: b value error b ^ parse error {c} 0 (function {c} returns _n instead of causing value error) ```...

"It seems it would have been easier to be consistent... ..." Agree - I think that the signal in this feature set is the presence or absence of the undefined...

- Projected arguments may skip positions Kona: ``` +[;2] +[;2] ``` K will appear to project but will not execute.

Partial list of bugs (or discrepancies) in Kx's K //K3.2: windows crash bug: (s;w) 0: (`f;0;1) where 1 is a bad length for `f //K3.2: Various "bugs" or strange inconsistencies...

More: * Load a file.txt with a million line parenthetical: \l file.txt /which has: `0:"hello";(1 2 1 1 ... /for a million rows 1 1) a:123 * _hash[1,][0] /more on...

> const values (e.g. 4 in "1 2 3 + 4") was very different than expected, Constants probably won't benefit from this change. It would be the output of combining...

This should be fairly simple. In the `plus(K x, K y)` primitive, for example, you can check that `y->c==1` and then invisibly set the return value of `z` to be...