4.9.1Guidelines for Using Assignment🔗 i

Although using set! is sometimes appropriate, Racket style generally discourages the use of set! . The following guidelines may help explain when using set! is appropriate.

• As in any modern language, assigning to a shared identifier is no substitute for passing an argument to a procedure or getting its result.

  Really awful example:

  (define name"unknown")

  (define result"unknown")

  (define (greet)

  (set! result(string-append "Hello, "name)))

  > (set! name"John")

  > (greet)

  > result

  "Hello, John"

  Ok example:

  (define (greetname)

  (string-append "Hello, "name))

  > (greet"John")

  "Hello, John"

  > (greet"Anna")

  "Hello, Anna"

• A sequence of assignments to a local variable is far inferior to nested bindings.

  Bad example:

  > (let ([tree0])

  (set! tree(list tree1tree))

  (set! tree(list tree2tree))

  (set! tree(list tree3tree))

  tree)

  '(((0 1 0) 2 (0 1 0)) 3 ((0 1 0) 2 (0 1 0)))

  Ok example:

  > (let* ([tree0]

  [tree(list tree1tree)]

  [tree(list tree2tree)]

  [tree(list tree3tree)])

  tree)

  '(((0 1 0) 2 (0 1 0)) 3 ((0 1 0) 2 (0 1 0)))

• Using assignment to accumulate results from an iteration is bad style. Accumulating through a loop argument is better.

  Somewhat bad example:

  (define (sumlst)

  (let ([s0])

  (for-each (lambda (i)(set! s(+ is)))

  lst)

  s))

  > (sum'(123))

  6

  Ok example:

  (define (sumlst)

  (let loop([lstlst][s0])

  (if (null? lst)

  s

  (loop(cdr lst)(+ s(car lst))))))

  > (sum'(123))

  6

  Better (use an existing function) example:

  (define (sumlst)

  (apply + lst))

  > (sum'(123))

  6

  Good (a general approach) example:

  (define (sumlst)

  (for/fold ([s0])

  ([i(in-list lst)])

  (+ si)))

  > (sum'(123))

  6

• For cases where stateful objects are necessary or appropriate, then implementing the object’s state with set! is fine.

  Ok example:

  (define next-number!

  (let ([n0])

  (lambda ()

  (set! n(add1 n))

  n)))

  > (next-number!)

  1

  > (next-number!)

  2

  > (next-number!)

  3

All else being equal, a program that uses no assignments or mutation is always preferable to one that uses assignments or mutation. While side effects are to be avoided, however, they should be used if the resulting code is significantly more readable or if it implements a significantly better algorithm.

The use of mutable values, such as vectors and hash tables, raises fewer suspicions about the style of a program than using set! directly. Nevertheless, simply replacing set! s in a program with vector-set! s obviously does not improve the style of the program.

4.9.2Multiple Values: set!-values 🔗 i

+Assignment: set! and set!-values in The Racket Reference also documents set!-values .

The set!-values form assigns to multiple variables at once, given an expression that produces an appropriate number of values:

(set!-values (id...)expr)

This form is equivalent to using let-values to receive multiple results from expr, and then assigning the results individually to the ids using set! .