Re:The Caves of Clojure part 3.1: World Generation
by stevelosh on Monday July 09, 2012 @03:23PM
(#4219908)
I don't get what you mean. I like the way new looks as compared to the Record. syntax, but either way you need the java class visible in the current namespace:
Is there another way to create record instances that doesn't involve that warty (import) call that I'm not aware of?
[ Parent
| on HN ]
Re:The Caves of Clojure part 3.1: World Generation
by bitsai on Monday July 09, 2012 @04:09PM
(#4220141)
As of Clojure 1.3, defrecord (and deftype) automatically define factory functions in the same namespace as the record itself. defrecord generates 2 such functions, one that takes positional arguments and one that takes a map. So once you have :use'd or :require'd the namespace, you can do stuff like the following without having to import anymore:
(->World [:foo])
(->World {:tiles [:foo]})
More details here:http://dev.clojure.org/display/design/defrecord+improvements
Re:The Caves of Clojure part 3.1: World Generation
by stevelosh on Monday July 09, 2012 @04:30PM
(#4220228)
Oh cool, I didn't know that. I kind of blocked 1.3 out of my memory after the "let's remove clojure.contrib and break everyone's shit" mess.
It's good to know that progress toward patching all the places Java tends to leak through into Clojure is happening.
I can't say I'm a fan of the punctuation-laden syntax, but I'll pick my battles and not complain about it.
I'll switch over to this new form tonight and mention it in one of the later posts. Thanks!
Re:The Caves of Clojure part 3.1: World Generation
by rapala on Tuesday July 10, 2012 @06:48AM
(#4222998)
This, and before 1.3 you were supposed to define a constructor function yourself. I'm pretty sure that was somewhere in the documentation. Or in the clojure.org/datatypes. Or in some mailing list post that I red. The Clojure documentation is a mess.