Louis Jenkins

@KING-SID I think that's something to propose in the design, i.e proposing what both versions would look like.

I prefer having a default argument with `where` clauses to perform pattern matching. ```chapel // Default action: ANY proc binarySearch(data, val, cmp, lo, hi, param direction = ANY) where direction...

Hm, I guess you're right. I was placing more emphasis on using pattern-matching `where` clauses than I should; personally I'd rather have it looks like this. ```chpl // Private function...

@bradcray As I said, it's more a preference towards pattern-matching and modularity. @KING-SID Imagine the case where you want either `FIRST`, `LAST`, or `ANY` based on some run-time variable or...

One more thing in favor of having a more modular interface is that you may want to add more cases, such as serial. ```chpl enum Direction { ANY = 0,...

1) There are optimizations you would make for sequential operations, such as not needlessly divide-and-conquer when you only have one thread, especially if you divide-and-conquer yourself. 2) It can result...

Your response of 'Chapel has a serial keyword... why not just rely on that rather than complicating the interface?' made me think that this would be the suggested solution for...