Re: [racket-users] From Clojure to Racket

2018-09-01 Thread Daniel Prager
Not quite string interpolation, but Racket also has (~a ...) with variable number of arguments, which I find convenient: E.g. (define x 5) (define y 6) (~a "x is " x " and y is " y " and x + y = " (+ x y)) ; "x is 5 and y is 6 and x + y = 11" Dan -- You received this message

Re: [racket-users] From Clojure to Racket

2018-08-31 Thread Ben Greenman
+1, especially for the at-exp post -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit

Re: [racket-users] From Clojure to Racket

2018-08-31 Thread Ben Kovitz
On Thursday, August 23, 2018 at 3:48:03 PM UTC-4, Greg Hendershott wrote: > This is a bit rough and old but: > > https://github.com/greghendershott/racket-clojure-cheat-sheet > You are too modest! I found your blog, and it's definitely got the kind of information I'm looking for. For

Re: [racket-users] From Clojure to Racket

2018-08-28 Thread Dave McDaniel
> > I'm asking for something much smaller than a User's Guide, though: a little > collection of the down-and-dirty stuff that you need to know to be > productive, > beyond knowing the syntax and semantics of the language. > While I expected a little more content for something with weekend in

Re: [racket-users] From Clojure to Racket

2018-08-25 Thread Neil Van Dyke
Hendrik Boom wrote on 08/25/2018 12:14 PM: Suggesting that sections in the Guide and Refernce manual should perhaps link to one another. There are already some such links, and it only helps me a little.  I think probably different people have different usage scenarios and ways of using the

Re: [racket-users] From Clojure to Racket

2018-08-25 Thread Hendrik Boom
On Fri, Aug 24, 2018 at 10:27:56PM -0400, Neil Van Dyke wrote: > Ben Kovitz wrote on 08/24/2018 10:04 PM: > > I noticed the separate User's Guide and Reference, and indeed that's one > > reason I'm considering Racket for practical use right now. > > The separation of a Guide is good for a

Re: [racket-users] From Clojure to Racket

2018-08-24 Thread Ben Greenman
The Racket Cheat Sheet might help: http://docs.racket-lang.org/racket-cheat/index.html -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [racket-users] From Clojure to Racket

2018-08-24 Thread Neil Van Dyke
Ben Kovitz wrote on 08/24/2018 10:04 PM: I noticed the separate User's Guide and Reference, and indeed that's one reason I'm considering Racket for practical use right now. The separation of a Guide is good for a read-through, like on the train, when first exposed to a system.  *But*, for

Re: [racket-users] From Clojure to Racket

2018-08-24 Thread Ben Kovitz
On Friday, August 24, 2018 at 9:33:12 PM UTC-4, Robby Findler wrote: > The racket documentation is organized into two documents. > … > Guide: http://docs.racket-lang.org/guide/define-struct.html > > Reference: http://docs.racket-lang.org/reference/define-struct.html I noticed the separate

Re: [racket-users] From Clojure to Racket

2018-08-24 Thread Robby Findler
The racket documentation is organized into two documents. One that is intended to be the useful, commonly-used bits (called the guide) and one is intended to be comprehensive, showing every possibly knob and button (called the reference). If you don't know about that, it can be easy to flip into

Re: [racket-users] From Clojure to Racket

2018-08-24 Thread Ben Kovitz
On Friday, August 24, 2018 at 8:39:43 PM UTC-4, Miodrag Milenkovic replied to me: >> Ah, thanks! I spent about an hour trying to figure out inspectors and didn't get anywhere, and I never would have guessed that :transparent means to make the struct printable. This is the kind of thing I'm

Re: [racket-users] From Clojure to Racket

2018-08-24 Thread Miodrag
:transparent is definitely mentioned in the guide chapter on structures, maybe ch 5 On Fri, Aug 24, 2018 at 8:15 PM Ben Kovitz wrote: > On Thursday, August 23, 2018 at 2:49:32 PM UTC-4, David K. Storrs wrote: > > For me, the first resorts in Racket are list and hash. If I'm going to do >> any

Re: [racket-users] From Clojure to Racket

2018-08-24 Thread Ben Kovitz
On Thursday, August 23, 2018 at 2:49:32 PM UTC-4, David K. Storrs wrote: For me, the first resorts in Racket are list and hash. If I'm going to do > any heavy lifting with it then I move to struct: > > (hash 'username 'bob 'age 18) ; quick and easy, works well with database, > useful print

Re: [racket-users] From Clojure to Racket

2018-08-23 Thread Greg Hendershott
Sorry -- realized I missed your last paragraph. I like other people's suggestions so far and will try to write up more later. On Thu, Aug 23, 2018 at 3:47 PM Greg Hendershott wrote: > > This is a bit rough and old but: > > https://github.com/greghendershott/racket-clojure-cheat-sheet --

Re: [racket-users] From Clojure to Racket

2018-08-23 Thread Greg Hendershott
This is a bit rough and old but: https://github.com/greghendershott/racket-clojure-cheat-sheet -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [racket-users] From Clojure to Racket

2018-08-23 Thread David Storrs
On Thu, Aug 23, 2018 at 1:02 PM Ben Kovitz wrote: > > In Clojure, the data structures of first resort are map and vector. > What's the equivalent in Racket--the short list of bread-and-butter data > structures that you reach for first when writing production code? How do > you, say,

[racket-users] From Clojure to Racket

2018-08-23 Thread Ben Kovitz
Has anyone written a guide for someone familiar with Clojure to get up to speed quickly with Racket? If not, I'd be willing to collaborate on writing one, if you'd be willing to spend a day or two showing me how to do things in Racket. Here's why I'm asking. I wrote a bunch of code in Clojure