Problems:
- completeness and consistency: need to be able to read and write records like other Clojure types
- dynamism: need to create defrecords without class-in-hand. Performantly, of course
- convenience: want map-like construction instead of positional slotwise construction
Open questions:
- modularity friendliness
- print/read syntax
There are a few tickets waiting on design decisions: - print/read syntax for defrecords
- record multimethod
Some (non-contributed) code that demonstrates people's need for this:
- cemerick's defrecord slot defaults
- David McNeil's enhanced clojure records
Labels: