modes should work for categorical data about code.pyret.org

[asolove]

Gonna close this out as the resolution won't be in the CPO codebase. But it's still on my backlog list so I'll write some suggested changes to that file and share with you.

[asolove]

Started looking at this one, some notes so I don't forget when I come back to this:

• The resolution of this will need to be over in pyret-lang, which defines the statistics package.

• The interesting bit here is that the definitions are currently typed for numbers and the implementations depend on that for efficiency, so we'll need to:

  • Convert all these methods to be generic or just add a second set of parallel methods for strings. (Do we want to allow over arbitrary types? I don't think Pyret has a notion of generic constraints, and we'd like to constrain this to things where equality is reasonable. I also don't think we want arbitrary mixed types.)
  • convert the implementation of group-and-count, which currently depends on the runtime helper raw_array_sort_nums to an alternative that will work for other types. (We probably still want to use the fast version for numbers, though?)

[asolove]

Related discussion over in pyret-lang, mostly around actually enforcing the type constraint and showing a nicer error, rather than extending these to other types: brownplt/pyret-lang#1538

[schanzer]

@asolove oh wow - really interesting to see that thread. I didn't realize this came up 2 years ago! In that case, maybe the solution is just a written-in-pyret-function that lives in our Data Science library. Would you be willing to write one?

[asolove]

Yeah, we could definitely do that. Can you point me to the Data Science library?

[schanzer]

Here's the link - I'm sure I'm not doing the most elegant stuff, so any advice you have on coding quality is most welcome!

[blerner]

Closing this as dupe of brownplt/pyret-lang#1538, since the discussion there is further along.