Turn the KomposDemo into benchmark, and optimize ValueCheckNode #350
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a working version of the KomposDemo as an actor benchmark.
To optimize compilation, the PR also improves the ValueCheckNode.
The initial version simply iterated over all object fields and checked whether each of them contains null or a value.
The optimized version creates a tester that has the accessors for the object fields, and uses them to check with a dedicated IsValue node whether the relevant fields contain values.
@sophie-kaleba this is perhaps an interesting optimization for you.
@daumayr I hope this is what we can use for the revision. I was thinking, maybe we want to add a use of STM to it though.