3 ms·
Referential transparency is not a lie; getA is just a value. It could be substituted for its meaning without altering the program. For example, the following pr
by chongli 13y ago
Referential transparency is not a lie; getA is just a value. It could be substituted for its meaning without altering the program. For example, the following program:
foo = do
a <- getA
putStrLn ("Hello, " ++ a ++ "!")
where
getA = do putStrLn "What is your name?"
getLine
Is equivalent to:
bar = do
a <- do putStrLn "What is your name?"
getLine
putStrLn ("Hello, " ++ a ++ "!")
- k_bx 13y agoYes, that's exactly what I was sayint 2 comments upper this thread: > The point I wanted to make is that it's the same getA, but anyone reading the code should understand that result binded to a and b will be different. So, while referrential transparency is still in place, programmer who reads the code will most likely care not about getA's result, but rather what will a and b get binded to, and in those terms it's just the same as good old a = getA(); b = getA();