Re:Should function arguments be reassignable or mutable?
by weinzierl on Monday January 01, 2018 @10:33AM
(#16046398)
The warning says it right away, the first a is shadowed, not reassigned, here.
The difference is that when a is reassigned the 7 is lost, while it should be still around when shadowed. I don‘t know of a way to access the 7 in this example however.
Re:Should function arguments be reassignable or mutable?
by runeks on Monday January 01, 2018 @04:34PM
(#16048171)
If there’s no way to access the 7 after it’s shadowed, why couldn’t an optimized garbage collector throw it away after it’s shadowed, thus making it equivalent to reassignment?
Re:Should function arguments be reassignable or mutable?
by maxxxxx on Monday January 01, 2018 @10:56AM
(#16046499)
Why would they allow this? Is there any legitimate case where doing this makes sense? Seems very risky to me. In most languages I know you would expect that the "a" variables are the same.
Re:Should function arguments be reassignable or mutable?
by christophilus on Monday January 01, 2018 @11:36AM
(#16046678)
In the past, I've used it in order to ensure the variable has a legitimate value. So, something like this (pseudo code):
fn foo(a):
a = a |> trim |> (default "chocolate")
mix a "milk"
Well, in this contrived example, I wouldn't reassign a, just tack on `|> (mix "milk")` but in a complex example where you're reusing `a` in several places, it can make sense and is nicer than having to declare a bunch of variables just to hold the sanitized values of arguments.
This is perfectly valid Haskell:
but you'll get a warning for it: tmp.hs:4:7: warning: This binding for ‘a’ shadows the existing binding bound at tmp.hs:2:7