Re: [RFC] Comparison and conversion inconsistency - need more info

> I didn't immediately spot it, but the word "comparable" next to each > argument in the Parameters section is linked to the comparison operators > page. It mgiht be an idea to add it to the See Also section as well, to > make it more visible. Don't see how this has any more of a visibility problem than mixed type params for other functions. IMO, it's a nice convenience that the hyperlink is there, but not even necessary. min(<list>) should be assumed to be sort(<array>) and unshift(<array>). Sort --> comparison --> comparison rules apply. Do we really have to reiterate anywhere that a comparison might be performed that it's going to follow comparison rules? If a fn accepts a callback, do we say, "Remember how comparisons work"? -- S.