14

I am having some troubles figuring how to use the "let" form. In the example below, I would like to locally bind the value "cols" in order to work on it later in the function. What I am noticing, however, is that if I use "let" the function sel-opt-tmp will return a nil value instead than a list.

(defn sel-opt-tmp []
  (let [cols "test"]))

(prn (sel-opt-tmp))

*The above code returns a nil value.

I understand that "let" only binds a value in the scope of a function, what I do not know is if there is a way to pass the value out of the let scope. Maybe there is something like "return" that I am not aware of? Or this is simply bad design and I should not use the binding at all in this case (this tends to create long chains of functions that are difficult to read although)?

kfk
  • 831
  • 2
  • 12
  • 25
  • 2
    The `let` form implicitly returns the last expression it contains, which in your case is the invisible `nil`. You need to use `cols` in the body of the `let` form to have it returned. – seh Nov 18 '11 at 17:03
  • `"let" only binds a value in the scope of a function` -- that's not quite true. `let`s can appear most anywhere, and the scope of the bound names is the `let` expression. – Matt Fenwick Nov 19 '11 at 13:45

2 Answers2

23

It returns nil because the contents of the let statement is empty (or nil). Try:

(let [cols "test"] cols)

Which will return the value of cols. As seh says, a let statement evaluates to the value of its last sub-expression.

Adrian Mouat
  • 44,585
  • 16
  • 110
  • 102
3

There is no such problem with passing values outside the scope as you mention. The binding cols is in force only within the scope, but the lifetime of the value of (:ks cols) is not similarly restricted. (That's why you have garbage collection: you can return values that point to data, and the data stays live as long as there are references to it.)

If you get nil from the function, that likely means that cols does not have a :ks key... or indeed might not be a map. Since cols is the result from filter, it is a sequence, and when the :ks keyword is used as a function, it returns nil for non-collections. To guard against that kind of bugs it may be a useful convention to always write (cols :ks) instead of (:ks cols) so that you get an error when what you think is a map is something else.

Jouni K. Seppänen
  • 43,139
  • 5
  • 71
  • 100