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
There seems to be a bit of delay from adding atom into space to having it be visible for query. Is add-atom intended to be asynchronous?, if not this is a legitimate bug. Take the following program:
This basically checks if the previous number is added. If not added then stops, otherwise adds the current number and continue. This should run up to the limit of 2000. Curiously the output stops at 71, [(Stopped At 71)]. However, if we go into repl right afterwards, we can verify that 71 does indeed exist with (match &self (Value 71) exists). This suggests there is a delay between add-atom in the second let* and match query in the first let*.
The text was updated successfully, but these errors were encountered:
There seems to be a bit of delay from adding atom into space to having it be visible for query. Is
add-atom
intended to be asynchronous?, if not this is a legitimate bug. Take the following program:This basically checks if the previous number is added. If not added then stops, otherwise adds the current number and continue. This should run up to the limit of 2000. Curiously the output stops at 71,
[(Stopped At 71)]
. However, if we go into repl right afterwards, we can verify that 71 does indeed exist with(match &self (Value 71) exists)
. This suggests there is a delay betweenadd-atom
in the secondlet*
andmatch
query in the firstlet*
.The text was updated successfully, but these errors were encountered: