Re: [racket-dev] collections with no one responsible
On Fri, Feb 3, 2012 at 6:32 PM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: Currently, the following collections have no one listed as responsible, along with who i think should be assigned to them: - mzlib (mflatt) Done. Any objections to this? If not, I'll do this soon. As well as: - gui-builder No one has made significant changes (other than collection-wide cleanups) to guibuilder in more than 6 years, except Asumu. Asumu, do you want to take this on? Asumu suggests removing this collection entirely. Is there any reason to keep it? - eopl Various people have changed this collection in the past few years (robby, eli, mflatt). Who should I assign bugs to? If no one is maintaining this code, would it be better for EOPL to distribute a PLT file? -- sam th sa...@ccs.neu.edu _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] collections with no one responsible
On Fri, Feb 3, 2012 at 7:47 PM, Eli Barzilay e...@barzilay.org wrote: An hour ago, Sam Tobin-Hochstadt wrote: Currently, the following collections have no one listed as responsible, along with who i think should be assigned to them: - tests (eli, mflatt) -- just the top level directory, not the subdirectories - mzlib (mflatt) - info-domain (mflatt) -- NB: contains no source files tests and info-domain are not collections, and there shouldn't be a default responsible for them. Fine for `info-domain'. For `tests', there are currently 3 files with no one responsible at the top level: - eli-tester.rkt - info.rkt - run-automated-tests.rkt I think they should all have you as responsible, and I'll leave the dir the way it is. Does that seem reasonable? -- sam th sa...@ccs.neu.edu _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] collections with no one responsible
Just now, Sam Tobin-Hochstadt wrote: For `tests', there are currently 3 files with no one responsible at the top level: - eli-tester.rkt - info.rkt - run-automated-tests.rkt I think they should all have you as responsible, and I'll leave the dir the way it is. Does that seem reasonable? Yes. [Fine for the first (which would eventually move to a proper place), and for the second (meaningless for drdr, but fine for the janitorial stuff). I guess that the third is fine for the same reason.] The obvious problem with a default owner is that new directories get added and inherit that owner. Also, it would be good to run a script that checks that all source files are owned. -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://barzilay.org/ Maze is Life! _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] collections with no one responsible
On Fri, Feb 17, 2012 at 8:52 AM, Eli Barzilay e...@barzilay.org wrote: Just now, Sam Tobin-Hochstadt wrote: For `tests', there are currently 3 files with no one responsible at the top level: - eli-tester.rkt - info.rkt - run-automated-tests.rkt I think they should all have you as responsible, and I'll leave the dir the way it is. Does that seem reasonable? Yes. [Fine for the first (which would eventually move to a proper place), and for the second (meaningless for drdr, but fine for the janitorial stuff). I guess that the third is fine for the same reason.] Done. The obvious problem with a default owner is that new directories get added and inherit that owner. Also, it would be good to run a script that checks that all source files are owned. Yes, that's a good idea. I'll do that. -- sam th sa...@ccs.neu.edu _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] collections with no one responsible
On Fri, Feb 17, 2012 at 7:43 AM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: - eopl Various people have changed this collection in the past few years (robby, eli, mflatt). Who should I assign bugs to? If no one is maintaining this code, would it be better for EOPL to distribute a PLT file? I don't think so, no. If the choices are between kicking it out and putting me on, put me on. I don't really know where that code came from, tho, and I didn't write it. Robby _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] collections with no one responsible
On Fri, Feb 17, 2012 at 9:06 AM, Matthew Flatt mfl...@cs.utah.edu wrote: At Fri, 17 Feb 2012 08:43:48 -0500, Sam Tobin-Hochstadt wrote: On Fri, Feb 3, 2012 at 6:32 PM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: As well as: - gui-builder No one has made significant changes (other than collection-wide cleanups) to guibuilder in more than 6 years, except Asumu. Asumu, do you want to take this on? Asumu suggests removing this collection entirely. Is there any reason to keep it? I agree with removing it. Done. -- sam th sa...@ccs.neu.edu _ Racket Developers list: http://lists.racket-lang.org/dev
[racket-dev] An Improvement to for/set
I've noticed myself desiring a for/set that would allow me to optionally add zero, one, or more elements to the accumulated set during each iteration. Is this something that other people would be interested in having in the set library? If so, I can send a pull request to the github repo. My implementation should be backwards compatible with the old one. I also created set-add* because I found myself wanting to add arbitrary numbers of elements to sets as well. ;; set-add* : [Set X] X ... - [Set X] (define (set-add* s . vs) (for/fold ((s s)) ((v vs)) (set-add s v))) (define-syntax (for/set stx) (syntax-case stx () [(_ clauses . body) #'(for/fold/derived stx ((accum-set (set))) clauses (call-with-values (lambda () . body) (curry set-add* accum-set)))])) Examples: (for/set ((x '(1 2 3 4 5))) (sqr x)) (set 1 4 9 16 25) (for/set ((x '(1 2 3 4 5))) (if (odd? x) x (values))) (set 1 3 5) -- Dan King College of Computer and Information Science Northeastern University _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] An Improvement to for/set
I would prefer a simpler for/union: (define-syntax (for/union stx) (syntax-case stx () [(_ clauses . body) #'(for/fold/derived stx ((accum-set (set))) clauses (set-union accum-set (let () . body))])) -Ian - Original Message - From: Daniel King dank...@ccs.neu.edu To: Racket Dev List dev@racket-lang.org Sent: Friday, February 17, 2012 1:07:25 PM GMT -05:00 US/Canada Eastern Subject: [racket-dev] An Improvement to for/set I've noticed myself desiring a for/set that would allow me to optionally add zero, one, or more elements to the accumulated set during each iteration. Is this something that other people would be interested in having in the set library? If so, I can send a pull request to the github repo. My implementation should be backwards compatible with the old one. I also created set-add* because I found myself wanting to add arbitrary numbers of elements to sets as well. ;; set-add* : [Set X] X ... - [Set X] (define (set-add* s . vs) (for/fold ((s s)) ((v vs)) (set-add s v))) (define-syntax (for/set stx) (syntax-case stx () [(_ clauses . body) #'(for/fold/derived stx ((accum-set (set))) clauses (call-with-values (lambda () . body) (curry set-add* accum-set)))])) Examples: (for/set ((x '(1 2 3 4 5))) (sqr x)) (set 1 4 9 16 25) (for/set ((x '(1 2 3 4 5))) (if (odd? x) x (values))) (set 1 3 5) -- Dan King College of Computer and Information Science Northeastern University _ Racket Developers list: http://lists.racket-lang.org/dev _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] collections with no one responsible
On Fri, Feb 17, 2012 at 8:58 AM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: Also, it would be good to run a script that checks that all source files are owned. Yes, that's a good idea. I'll do that. The .rkt files with no one responsible are (all in tests, with who I think should be assigned them): (mflatt?) collects/tests/errortrace/ collects/tests/aligned-pasteboard/ collects/tests/scriblib/ collects/tests/utils/ (ryanc?) collects/tests/data/heap.rkt collects/tests/data/ordered-dict.rkt collects/tests/data/queue.rkt collects/tests/data/order.rkt collects/tests/data/gvector.rkt (eli?) collects/tests/profile/main.rkt collects/tests/profile/topsort.rkt collects/tests/lazy/main.rkt collects/tests/lazy/forcers.rkt collects/tests/lazy/promise.rkt collects/tests/lazy/lang.rkt collects/tests/file/md5.rkt collects/tests/file/gzip.rkt collects/tests/file/main.rkt -- sam th sa...@ccs.neu.edu _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] collections with no one responsible
On Fri, Feb 17, 2012 at 9:00 AM, Robby Findler ro...@eecs.northwestern.edu wrote: On Fri, Feb 17, 2012 at 7:43 AM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: - eopl Various people have changed this collection in the past few years (robby, eli, mflatt). Who should I assign bugs to? If no one is maintaining this code, would it be better for EOPL to distribute a PLT file? I don't think so, no. If the choices are between kicking it out and putting me on, put me on. I don't really know where that code came from, tho, and I didn't write it. This doesn't really solve the question I started with, which is what should I tell people who report bugs. As I see it, there are basically 3 options: 1. Someone who's already maintaining other things starts genuinely maintaining the eopl collection. That sounds pretty unlikely to me, and I don't think that's what you're volunteering for. 2. We keep it where it is, and don't maintain the code other than fixing life-threating bugs. This is basically the status quo, and I think it means people who report other, non-life-threatening bugs should be informed that we're not maintaining the code, and thus their bug isn't going to get fixed. 3. We take eopl out of the tree, and it's distributed/maintained by Dan and Mitch (or by someone else). Choice 2 is reasonable, but we should be clear about it. -- sam th sa...@ccs.neu.edu _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] collections with no one responsible
Do we have any bugs in category 2.? Robby On Fri, Feb 17, 2012 at 4:38 PM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: On Fri, Feb 17, 2012 at 9:00 AM, Robby Findler ro...@eecs.northwestern.edu wrote: On Fri, Feb 17, 2012 at 7:43 AM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: - eopl Various people have changed this collection in the past few years (robby, eli, mflatt). Who should I assign bugs to? If no one is maintaining this code, would it be better for EOPL to distribute a PLT file? I don't think so, no. If the choices are between kicking it out and putting me on, put me on. I don't really know where that code came from, tho, and I didn't write it. This doesn't really solve the question I started with, which is what should I tell people who report bugs. As I see it, there are basically 3 options: 1. Someone who's already maintaining other things starts genuinely maintaining the eopl collection. That sounds pretty unlikely to me, and I don't think that's what you're volunteering for. 2. We keep it where it is, and don't maintain the code other than fixing life-threating bugs. This is basically the status quo, and I think it means people who report other, non-life-threatening bugs should be informed that we're not maintaining the code, and thus their bug isn't going to get fixed. 3. We take eopl out of the tree, and it's distributed/maintained by Dan and Mitch (or by someone else). Choice 2 is reasonable, but we should be clear about it. -- sam th sa...@ccs.neu.edu _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] collections with no one responsible
Sam Tobin-Hochstadt wrote at 02/17/2012 05:38 PM: 2. We keep it where it is, and don't maintain the code other than fixing life-threating bugs. This is basically the status quo, and I think it means people who report other, non-life-threatening bugs should be informed that we're not maintaining the code, and thus their bug isn't going to get fixed. Side comment, which will probably sound odd: I'm not sure if you mean life-threatening literally in this case, and I'm not criticizing that use, but I think probably best if people don't adopt this term and start using it loosely on the Racket email lists. I believe that some people on Racket lists also work on life-critical or safety-critical systems, and are all kinds of serious about it. Please to be gentle with delicate sensibilities of engineers. -- http://www.neilvandyke.org/ _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] collections with no one responsible
Yes, there are two of them at the moment. Those are the only bugs assigned to 'nobody' at the moment. However, since I sent the last email I've had a volunteer to maintain the eopl collection, so hopefully this story will have a happier ending than I expected. Sam On Feb 17, 2012 6:15 PM, Robby Findler ro...@eecs.northwestern.edu wrote: Do we have any bugs in category 2.? Robby On Fri, Feb 17, 2012 at 4:38 PM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: On Fri, Feb 17, 2012 at 9:00 AM, Robby Findler ro...@eecs.northwestern.edu wrote: On Fri, Feb 17, 2012 at 7:43 AM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: - eopl Various people have changed this collection in the past few years (robby, eli, mflatt). Who should I assign bugs to? If no one is maintaining this code, would it be better for EOPL to distribute a PLT file? I don't think so, no. If the choices are between kicking it out and putting me on, put me on. I don't really know where that code came from, tho, and I didn't write it. This doesn't really solve the question I started with, which is what should I tell people who report bugs. As I see it, there are basically 3 options: 1. Someone who's already maintaining other things starts genuinely maintaining the eopl collection. That sounds pretty unlikely to me, and I don't think that's what you're volunteering for. 2. We keep it where it is, and don't maintain the code other than fixing life-threating bugs. This is basically the status quo, and I think it means people who report other, non-life-threatening bugs should be informed that we're not maintaining the code, and thus their bug isn't going to get fixed. 3. We take eopl out of the tree, and it's distributed/maintained by Dan and Mitch (or by someone else). Choice 2 is reasonable, but we should be clear about it. -- sam th sa...@ccs.neu.edu _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] collections with no one responsible
5 hours ago, Sam Tobin-Hochstadt wrote: (eli?) collects/tests/profile/main.rkt collects/tests/profile/topsort.rkt collects/tests/lazy/main.rkt collects/tests/lazy/forcers.rkt collects/tests/lazy/promise.rkt collects/tests/lazy/lang.rkt collects/tests/file/md5.rkt collects/tests/file/gzip.rkt collects/tests/file/main.rkt I added all of these. -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://barzilay.org/ Maze is Life! _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Missing pregexp syntax in Racket
On November 29th 2011, Asumu Takikawa wrote: On 2011-11-29 15:43:27 -0500, Matthias Felleisen wrote: So, any volunteers? I added this to the list of intro projects on GitHub, so if anyone wants to take this up, please put it up on GitHub/PLaneT and update the page: https://github.com/plt/racket/wiki/Intro-Projects Isn't that what `parser-tools/lex-sre' implements? Also, is there any use for a Goops port? At least as far as CLOS-like OOs go, it's easy to build on an existing one instead of yet another implementation (it was the original point of CLOS). -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://barzilay.org/ Maze is Life! _ Racket Developers list: http://lists.racket-lang.org/dev
