[racket-dev] git rebase annoyances

2010-07-08 Thread Eli Barzilay
So, rebasing is a common operation since we're working with a central repository. But it's very annoying that files are touched whenever it happens. For example, you modify "collects/foo/bar.rkt", you then run a "git pull --rebase" to get updated with the current state, and since I pushed some ch

Re: [racket-dev] proposal: `data' collection

2010-07-08 Thread Stephen De Gabrielle
> 1. collect evidence that size matters to anyone out there besides you I'm happy to be a datapoint Size matters to me for three reasons; - startup time is significantly slowed on my (early 2010) MacBook pro given all the packages : - I disable all but the minimum to run on my ASus 701 4g which s

Re: [racket-dev] proposal: `data' collection

2010-07-08 Thread Matthias Felleisen
On Jul 8, 2010, at 1:46 PM, Eli Barzilay wrote: > But I still think that giving up on any organization will only make > things worse, and I don't want that to happen. Okay. As I wrote before: > For Chicago: > > 1. collect evidence that size matters to anyone out there besides you > > 2. pr

Re: [racket-dev] internal-definition parsing

2010-07-08 Thread Eli Barzilay
On Jul 8, Matthias Felleisen wrote: > On Jul 8, 2010, at 12:09 PM, Jay McCarthy wrote: > > > #%module-begin as the top level controlling macro is a distinguishing > > feature. Requires and provides can only be there and you know there's > > only one application. > > These could be an argument to

Re: [racket-dev] internal-definition parsing

2010-07-08 Thread Eli Barzilay
On Jul 8, Matthias Felleisen wrote: > > 2. I do not understand why #%body isn't enough. Couldn't #%body >locally expand to the point where defs and exps are >distinguished? Yes, it could -- and I guess that would be in analogy to `#%module-begin'. But I generally don't like that macros

Re: [racket-dev] proposal: `data' collection

2010-07-08 Thread Eli Barzilay
On Jul 8, Matthias Felleisen wrote: > This sounds like we should give up on stratification. That was my first thought when I saw that mess: give up also on distributing smaller packages, and dump the current distributions that are used as sanity checks. (Given that I usually end up in long thre

Re: [racket-dev] internal-definition parsing

2010-07-08 Thread Matthias Felleisen
On Jul 8, 2010, at 12:09 PM, Jay McCarthy wrote: > #%module-begin as the top level controlling macro is a distinguishing > feature. Requires and provides can only be there and you know there's > only one application. These could be an argument to the #%...-begin macro: are-you-top-level? :: (

Re: [racket-dev] internal-definition parsing

2010-07-08 Thread Jay McCarthy
On Thu, Jul 8, 2010 at 11:19 AM, Matthias Felleisen wrote: > > On Jul 7, 2010, at 5:55 PM, Eli Barzilay wrote: > >> Some examples that show how useful this is: >> >>  * In the lazy language you want the implicit begin to force all >>    expressions except for the last one. >> >>  * I've redefined

Re: [racket-dev] proposal: `data' collection

2010-07-08 Thread Matthias Felleisen
This sounds like we should give up on stratification. On Jul 7, 2010, at 5:21 PM, Eli Barzilay wrote: > On Jul 6, Petey Aldous wrote: >> That would be interesting and it would not be terribly difficult to >> instrument setup-plt to do it. > > There's no reason to do that -- the data is all t

Re: [racket-dev] internal-definition parsing

2010-07-08 Thread Matthias Felleisen
On Jul 7, 2010, at 5:55 PM, Eli Barzilay wrote: > Some examples that show how useful this is: > > * In the lazy language you want the implicit begin to force all >expressions except for the last one. > > * I've redefined the implicit begin (in an ugly way) for my course >language to f