Re: [racket-dev] What is the policy on what is included in the core libraries?
Somewhat related, would it make sense to add a function like stx-e that would be like (if (syntax? stx) (syntax-e stx) stx) to syntax/stx? On Feb 17, 2015, at 2:18 AM, Alexis King 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 racket-dev+unsubscr...@googlegroups.com. > To post to this group, send email to racket-...@googlegroups.com. > 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 racket-dev+unsubscr...@googlegroups.com. To post to this group, send email to racket-...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/B0E5B796-5C34-44E3-8B54-7A17169AF121%40knauth.org. For more options, visit https://groups.google.com/d/optout.
Re: [racket-dev] What is the policy on what is included in the core libraries?
(I was thinking dissertations.) On Feb 17, 2015, at 2:47 PM, Dan Burton 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 > 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 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 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 racket-dev+unsubscr...@googlegroups.com. > >>> To post to this group, send email to racket-...@googlegroups.com. > >>> 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 racket-dev+unsubscr...@googlegroups.com. > >> To post to this group, send email to racket-...@googlegroups.com. > >> 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 racket-dev+unsubscr...@googlegroups.com. > To post to this group, send email to racket-...@googlegroups.com. > 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 racket-dev+unsubscr...@googlegroups.com. To post to this group, send email to racket-...@googlegroups.com. 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.
Re: [racket-dev] What is the policy on what is included in the core libraries?
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 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 > 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 > 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 racket-dev+unsubscr...@googlegroups.com . > >>> To post to this group, send email to racket-...@googlegroups.com > . > >>> 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 racket-dev+unsubscr...@googlegroups.com . > >> To post to this group, send email to racket-...@googlegroups.com > . > >> 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 racket-dev+unsubscr...@googlegroups.com . > To post to this group, send email to racket-...@googlegroups.com > . > 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 racket-dev+unsubscr...@googlegroups.com. To post to this group, send email to racket-...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CALSygwe55dGK4KuCF1Esnm8a2%3DamfSTaDE-LR6iHpmUmhbHw8g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [racket-dev] What is the policy on what is included in the core libraries?
Yes, that's true. Robby On Tue, Feb 17, 2015 at 10:50 AM, Sam Tobin-Hochstadt wrote: > On Tue, Feb 17, 2015 at 11:31 AM, Jens Axel Søgaard > wrote: >> 2015-02-17 14:26 GMT+01:00 Robby Findler : >>> I don't think the libraries are sufficient as is, but I would resist >>> adding aliases. >> >> A alternative: Added the word zip to the documentation index, >> link it to map and have an example where in (map list ...) is used. > > Since `zip` isn't an alias for anything, I think we should add it. > > Sam -- 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 racket-dev+unsubscr...@googlegroups.com. To post to this group, send email to racket-...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAL3TdONe3-xhiVrpQ%3D8ZGc9AjYr9NBoxCj5JDVDdr0trckKPpw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [racket-dev] What is the policy on what is included in the core libraries?
At some point TR will move on, and perhaps the time has come. On Feb 17, 2015, at 12:06 PM, Vincent St-Amour 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 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 racket-dev+unsubscr...@googlegroups.com. >>> To post to this group, send email to racket-...@googlegroups.com. >>> 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 racket-dev+unsubscr...@googlegroups.com. >> To post to this group, send email to racket-...@googlegroups.com. >> 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 racket-dev+unsubscr...@googlegroups.com. To post to this group, send email to racket-...@googlegroups.com. 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.
Re: [racket-dev] What is the policy on what is included in the core libraries?
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 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 racket-dev+unsubscr...@googlegroups.com. > > To post to this group, send email to racket-...@googlegroups.com. > > 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 racket-dev+unsubscr...@googlegroups.com. > To post to this group, send email to racket-...@googlegroups.com. > 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 racket-dev+unsubscr...@googlegroups.com. To post to this group, send email to racket-...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/87d258qxg8.wl%25stamourv%40ccs.neu.edu. For more options, visit https://groups.google.com/d/optout.
Re: [racket-dev] What is the policy on what is included in the core libraries?
On Tue, Feb 17, 2015 at 8:26 AM, Robby Findler wrote: > I don't think the libraries are sufficient as is, but I would resist > adding aliases. > > Perhaps a better way to get people coming from Haskell would be to > write an essay specifically aimed there? > > - Step 1: use variables. > - Step 2: here are `for` loops! Instead of an essay, this could be a guide for Haskellers/MLers/ Whatever-ers, which would make it easy to get results into documentation searches, and that would make it easy to address issues that cannot be resolved with a new binding like the bad argument order in `take` or the different input function for the folds. (Another point for avoiding a `zip` binding is that it's much more likely to collide with user defined functions than it is in other languages.) -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://barzilay.org/ Maze is Life! -- 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 racket-dev+unsubscr...@googlegroups.com. To post to this group, send email to racket-...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CALO-gusXr5Di4GBb3-xi3R5sL8G1CcAfNs3%2BBOB-7uM_AavGvA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [racket-dev] What is the policy on what is included in the core libraries?
On Tue, Feb 17, 2015 at 11:31 AM, Jens Axel Søgaard wrote: > 2015-02-17 14:26 GMT+01:00 Robby Findler : >> I don't think the libraries are sufficient as is, but I would resist >> adding aliases. > > A alternative: Added the word zip to the documentation index, > link it to map and have an example where in (map list ...) is used. Since `zip` isn't an alias for anything, I think we should add it. Sam -- 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 racket-dev+unsubscr...@googlegroups.com. To post to this group, send email to racket-...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAK%3DHD%2BYOu17C96DO0q7HRw5yAQEK0aXurewX%3DeDYEMmHpAz%2BBg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [racket-dev] What is the policy on what is included in the core libraries?
2015-02-17 14:26 GMT+01:00 Robby Findler : > I don't think the libraries are sufficient as is, but I would resist > adding aliases. A alternative: Added the word zip to the documentation index, link it to map and have an example where in (map list ...) is used. Also: Isn't zip in srfi/1 ? /Jens Axel -- 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 racket-dev+unsubscr...@googlegroups.com. To post to this group, send email to racket-...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CABefVgz2g3svHzxg55Y11DWi%3DAKqm21YRvu777owxi4p_tqNNg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [racket-dev] What is the policy on what is included in the core libraries?
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 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 racket-dev+unsubscr...@googlegroups.com. > To post to this group, send email to racket-...@googlegroups.com. > 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 racket-dev+unsubscr...@googlegroups.com. To post to this group, send email to racket-...@googlegroups.com. 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.
Re: [racket-dev] What is the policy on what is included in the core libraries?
I don't think the libraries are sufficient as is, but I would resist adding aliases. Perhaps a better way to get people coming from Haskell would be to write an essay specifically aimed there? - Step 1: use variables. - Step 2: here are `for` loops! ;) Robby On Tue, Feb 17, 2015 at 1:18 AM, Alexis King 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 racket-dev+unsubscr...@googlegroups.com. > To post to this group, send email to racket-...@googlegroups.com. > 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 racket-dev+unsubscr...@googlegroups.com. To post to this group, send email to racket-...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAL3TdONpdpZX%3D63ZtmPxTytPfw_PrL6gR6dwQXcbnS5_cB2OcQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[racket-dev] What is the policy on what is included in the core libraries?
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 racket-dev+unsubscr...@googlegroups.com. To post to this group, send email to racket-...@googlegroups.com. 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.
