-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup code in IdExecutionInstrument #7811
Conversation
public interface IdExecutionService { | ||
String INSTRUMENT_ID = "id-value-extractor"; | ||
|
||
public interface Callbacks { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hubertp , @4e6: one of the goals on the path towards running language server as guest Java/JS/Enso code
is to identify what kind of interface we need between the engine and the guest code to track execution. This is the interface. These four callback methods are enough to implement the execution tracking functionality of language server.
Next step. Use them from Enso, somehow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks sane
Pull Request Description
As part of investigation of #7683, let's make
IdExecutionEventNode
smaller by having a reference to factory and its fields.Important Notes
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:
Scala,
Java,