You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then there should be a discussion on why Haskell, in general, does not have observable sharing. Answer, because that breaks referential transparency. That is, if you can tell if two pointers are equal then a function can produce different outputs from the same inputs.
The text was updated successfully, but these errors were encountered:
In the glossary I link to the wikipedia entry for closures. This is lazy, cite the lambda papers!
similarly in the sharing item I don't cite anything. This is also lazy! I should cite at least:
Then there should be a discussion on why Haskell, in general, does not have observable sharing. Answer, because that breaks referential transparency. That is, if you can tell if two pointers are equal then a function can produce different outputs from the same inputs.
The text was updated successfully, but these errors were encountered: