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
Besides Fun, Comm and Num pointers should also be callable objects as long as opening them reveals a Fun. For example, the three following expressions should reduce to the same value:
((lambda (x) x) nil)
((commit (lambda (x) x)) nil)
((num (commit (lambda (x) x))) nil)
The text was updated successfully, but these errors were encountered:
@porcuquine I just realized that expressions like (1 2 3) will error in a non provable way because of the failure to open the commitment on the head. Let me know if we should follow the plan to include nums or if we should only support comms.
Besides
Fun
,Comm
andNum
pointers should also be callable objects as long as opening them reveals aFun
. For example, the three following expressions should reduce to the same value:((lambda (x) x) nil)
((commit (lambda (x) x)) nil)
((num (commit (lambda (x) x))) nil)
The text was updated successfully, but these errors were encountered: