(I was thinking dissertations.)
On Feb 17, 2015, at 2:47 PM, Dan Burton <[email protected]> wrote: > Matthias, when you say "At some point TR will move on," what do you mean by > that? I, for one, would like to see TR more tightly integrated with regular > racket a la progressive types, rather than branching off into its own arena. > > On Tuesday, February 17, 2015, Matthias Felleisen <[email protected]> > wrote: > > At some point TR will move on, and perhaps the time has come. > > > On Feb 17, 2015, at 12:06 PM, Vincent St-Amour <[email protected]> wrote: > > > I don't think we should add functions to TR that are not in Racket and > > that are not clearly type-related (e.g., `cast`). > > > > I also like Jens's solution better. Education vs crutches. > > > > Vincent > > > > > > > > At Tue, 17 Feb 2015 10:39:16 -0500, > > Matthias Felleisen wrote: > >> > >> > >> I'd add them to Typed Racket. That's what Haskellians are most likely to > >> explore and when they find them, it's a good thing (tm). -- Matthias > >> > >> > >> > >> > >> On Feb 17, 2015, at 2:18 AM, Alexis King <[email protected]> wrote: > >> > >>> I was just thinking today that I would, for example, find it useful to > >>> have a (zip ...) function in racket/list that would be equivalent to (map > >>> list ...). Users coming from a Haskell background might even find it > >>> useful to have a zip-with function that is simply an alias for map. > >>> Admittedly, these are rather trivial, but (especially in the first case) > >>> I think they’d still be useful. > >>> > >>> I am all for avoiding feature creep and code bloat, but Racket’s > >>> “batteries included” approach seems to make functions like these prime > >>> candidates for libraries like racket/list. As long as they’re not in > >>> racket/base, they seem fairly harmless, especially considering they would > >>> only be needed at compile-time. > >>> > >>> Should I even consider adding things like this, or is the consensus that > >>> the libraries are mostly sufficient as-is? > >>> > >>> -- > >>> You received this message because you are subscribed to the Google Groups > >>> "Racket Developers" group. > >>> To unsubscribe from this group and stop receiving emails from it, send an > >>> email to [email protected]. > >>> To post to this group, send email to [email protected]. > >>> To view this discussion on the web visit > >>> https://groups.google.com/d/msgid/racket-dev/5D941DB1-8A55-4A41-98A2-A3BE1BFE6D40%40gmail.com. > >>> For more options, visit https://groups.google.com/d/optout. > >> > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Racket Developers" group. > >> To unsubscribe from this group and stop receiving emails from it, send an > >> email to [email protected]. > >> To post to this group, send email to [email protected]. > >> To view this discussion on the web visit > >> https://groups.google.com/d/msgid/racket-dev/EAAD5B93-DB78-419B-A662-131AD1D3E303%40ccs.neu.edu. > >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Racket Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/racket-dev/63C7696A-1532-400A-825D-247BB3E31750%40ccs.neu.edu. > For more options, visit https://groups.google.com/d/optout. > > > -- > -- Dan Burton -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/31B41614-950F-49D8-AB81-D237FD917DB3%40ccs.neu.edu. For more options, visit https://groups.google.com/d/optout.
