“define a procedure ‘reduce-per-key’ which a procedure reducef and a list of associations in which each key is paired with a list. The output is a list of the same structure except that each key is now associated with the result of applying reducef to its associated list”
I’ve already written ‘map-per-key’ and ‘group-by-key’ :
(define (map-per-key mapf lls)
(cond
[(null? lls) '()]
[else (append (mapf (car lls))(map-per-key mapf (cdr lls)))]))
(define (addval kv lls)
(cond
[(null? lls) (list (list (car kv)(cdr kv)))]
[(eq? (caar lls) (car kv))
(cons (list (car kv) (cons (cadr kv) (cadar lls)))(cdr lls))]
[else (cons (car lls)(addval kv (cdr lls)))]))
(define (group-by-key lls)
(cond
[(null? lls) '()]
[else (addval (car lls) (group-by-key (cdr lls)))]))
how would I write the next step, ‘reduce-per-key’ ? I’m also having trouble determining if it calls for two arguments or three.
so far, I’ve come up with:
(define (reduce-per-key reducef lls)
(let loop ((val (car lls))
(lls (cdr lls)))
(if (null? lls) val
(loop (reducef val (car lls)) (cdr lls)))))
however, with a test case such as:
(reduce-per-key
(lambda (kv) (list (car kv) (length (cadr kv))))
(group-by-key
(map-per-key (lambda (kv) (list kv kv kv)) xs)))
I receive an incorrect argument count, but when I try to write it with three arguments, I also receive this error. Anyone know what I’m doing wrong?
Your solution is a lot more complicated than it needs to be, and has several errors. In fact, the correct answer is simple enough to make unnecessary the definition of new helper procedures. Try working on this skeleton of a solution, just fill-in the blanks:
Remember that there’s a built-in procedure for mapping a function over a list. Test it like this:
Notice that each association is composed of a key (the
carpart) and a list as its value (thecdrpart). For example:As a final thought, the name
reduce-per-keyis a bit misleading,map-per-keywould be a lot more appropriate as this procedure can be easily expressed usingmap… but that’s left as an exercise for the reader.UPDATE:
Now that you’ve found a solution, I can suggest a more concise alternative using
map: