Hi Alexis Nice!
I've been playing with Clojure a bit recently and I 1. several aspects (like the generic operations, concise destructuring, etc.), 2. am frustrated with others (e.g. error messages and tooling), 3. are intrigued by some of the other design choices (e.g. pervasive use of persistent data structures) So I see what you're doing as exciting, but would appreciate a bit more about where you're aiming to take this in your introduction. If you could outline your criteria / aims that would be clarifying. Are you aiming for consistency with Clojure or making a judgement call on an intermediate style (c.f. Greg's #lang rackjure)? * * * Some inconsistent-feeling behaviors: > (take 5 (range 10)) #<lazy-sequence> > (drop 5 (range 10)) '(5 6 7 8 9) > (take 5 #(0 1 2 3 4 5 6 7 8 9)) #<lazy-sequence> > (drop 5 #(0 1 2 3 4 5 6 7 8 9)) #<random-access-sequence> > (take 5 (list->vector (range 10))) take: contract violation Dan -- 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 https://groups.google.com/d/optout.
