2 ms·
Truly a nit-pick, but referential transparency is used wrongly by basically every FP-language for some reason. What they actually mean there is pureness, not re
by kaba0 5y ago
Truly a nit-pick, but referential transparency is used wrongly by basically every FP-language for some reason. What they actually mean there is pureness, not referential transparency - it is pureness that allows the replacement of a function call with its result, not any other feature of a language.
Hell, Java may actually be more referentially transparent than Haskell, due to it not having macros - the one thing that can break this functionality.