Kurtis Rader

@iandol, I noticed the issue you asked about, vis-a-vis manipulating lists, long ago but didn't open an issue because it was only recently that I started writing non-trivial Elvish programs;...

Note that commit 0b0f5ba8678e5d8cb5274fb56769f4a340b0d48a introduced a [`conj`](https://elv.sh/ref/builtin.html#conj) command to efficiently append to a list. Since the commit comment does not refer to an issue, and is quite terse, it is...

> You can't depend on the existence of cat or grep on Windows, but there's still a need to write scripts that are portable across UNIX flavors and sometimes that...

Ugh! My "P.S." in my opening comment of this issue is obviously bogus since `var arg-specs` is defining a map, independent of the behavior of `flag:parse-getopt`. W don't want to...

> What is so special in the keys $map | order bit, that we should, in your opinion, make sure that it never fails? Precisely because Elvish map keys are...

I get your point, @dunsany; however, I would argue that it may be desirable this example provides an ordered output rather than raise an exception: ``` > order [1 (num...

@dunsany: This came to my attention again while working on issue #1495 to sort the keys of maps printed by `pprint` and `repr`. There is a world of difference between...

@xiaq, Having worked on a solution to issue #1495 I now have an even stronger belief that an explicit ordering of incomparable types should be defined (as in my earlier...

I modified the [`cmp`](https://github.com/elves/elvish/blob/de8e5f2fd637567d7c1c6ffd7b9e0dcc506eb6a4/pkg/eval/builtin_fn_pred.go#L83) function to replace the "uncomparable" return value with an explicit ordering of uncomparable types as I proposed in an earlier [comment](https://github.com/elves/elvish/issues/1599#issuecomment-1214583787). I was pleasantly surprised at...

In light of my previous comment and thinking about the unit test failures I have concluded that the new behavior should not be the default. It should require an explicit...