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
Decide how to handle the async Python stuff. Currently, this is mostly "not supported" and yields a ProblemNode.
Ideas:
these are basically the same as the non-async stuff -> make them inherit from the non-async classes and use the same functions in the handlers.
Pro: less duplicate code 👍
Con: this violates the Python AST grammar where they do not inherit form the non-async classes. I would like to have this reflected in our code (I only care about the Python.kt file here. If someone knows some kotlin magic to keep them separated there and still use the same implementations in the handlers 🥳 ).
keep them separate -> duplicate code. We still need to implement (copy) the async stuff then.
better ideas?
The text was updated successfully, but these errors were encountered:
Decide how to handle the
async
Python stuff. Currently, this is mostly "not supported" and yields aProblemNode
.Ideas:
Python.kt
file here. If someone knows some kotlin magic to keep them separated there and still use the same implementations in the handlers 🥳 ).The text was updated successfully, but these errors were encountered: