I've been trying to figure why some binding is giving me a stack
overflow and I've discovered that if you use the BindHelpers.bind
method with a set of function BindParams, all the functions are
evaluated regardless of whether a match is found.
So, for example, if you bind to an empty NodeSeq and have a BindParam
which will never match like:
"you won't find me here" -> { print("Got here!");
NodeSeq.Empty }
…you find that the print statement is called.
This really surprised me. Is this intentional behaviour as it seems
to be a potential source of significant redundant processing?
Stuart.
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en.
