On Tue, Feb 17, 2015 at 8:49 PM, Matthias Felleisen
matth...@ccs.neu.edu wrote:
On Feb 17, 2015, at 7:59 PM, Sam Tobin-Hochstadt wrote:
I expect that the packages that update for Matthias on `make` are
packages in main-distribution,
Personally, I have used the 'same' one-line command
Hello,
I am working on porting the racket compiler to racket. But it still has a
bit to go and I have not yet ported the optimizer. So go right ahead.
Thank you.
~Leif Andersen
On Sun, Feb 15, 2015 at 1:36 PM, Gustavo Massaccesi gust...@oma.org.ar
wrote:
There is project to rewrite the
2015-02-17 14:26 GMT+01:00 Robby Findler ro...@eecs.northwestern.edu:
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:
On Tue, Feb 17, 2015 at 8:26 AM, Robby Findler
ro...@eecs.northwestern.edu 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
On Tue, Feb 17, 2015 at 11:31 AM, Jens Axel Søgaard
jensa...@soegaard.net wrote:
2015-02-17 14:26 GMT+01:00 Robby Findler ro...@eecs.northwestern.edu:
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
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
At some point TR will move on, and perhaps the time has come.
On Feb 17, 2015, at 12:06 PM, Vincent St-Amour stamo...@ccs.neu.edu 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
Sam and I have run into a situation where `make` fails because we've
set up clone pkgs and made local modifications in a way that makes the
git commands fail [*].
My guess is that the right thing to do is for me to know about these
pkgs and do something special when running make. I'm thinking
I think there are two seperable issues here:
1. Can we make `raco pkg update -a` better/more robust in this case?
2. Should `make` run `raco pkg update -a`?
In reverse order:
- I think `make`, by default, shouldn't update anything, and that we
should have a different Makefile target which
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 lexi.lam...@gmail.com wrote:
I was just thinking today that I would, for example, find it useful to have a
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
Yes, that's true.
Robby
On Tue, Feb 17, 2015 at 10:50 AM, Sam Tobin-Hochstadt
sa...@cs.indiana.edu wrote:
On Tue, Feb 17, 2015 at 11:31 AM, Jens Axel Søgaard
jensa...@soegaard.net wrote:
2015-02-17 14:26 GMT+01:00 Robby Findler ro...@eecs.northwestern.edu:
I don't think the libraries are
12 matches
Mail list logo
