i would prefer that we make Console and Workspace ...
# development
a
i would prefer that we make Console and Workspace special rather than making the rules special
w
they are. but we also don’t want them used elsewhere in the graph
👍 1
because concurrency that we don’t really have a handle on
👍 1
a
i guess i buy that. can’t think of a neat way to do that atm
thanks
h
there's a
side_effecting
class annotation that these types have
👍 1
a
that’s what i was thinking of extending somehow
h
actually wait -
Console
has both the side_effecting class attr and an a
@side_effecting
annotation
I think the former is redundant now
w
biiig tangent, but
i expect that there is a path forward for those types that involves “acquiring” an async lock on them before interacting with them
👍 1
a
i would love to see that
w
and that that would also be how we allowed multiple goals to run concurrently, but complete in some order
(having said that, we probably still would only want goal_rules to consume them, even in that world… unclear)
a
(i also want to compile
@rule
python code to webassembly to avoid GIL blocking in the very far future)
w
there are possibilities there, yea. see also https://github.com/RustPython/RustPython
🔥 1
very, very distant though, i expect.
👍 1
a
great link, that's super cool