[ET-VK] Separate OpNode to PrepackNode/ExecuteNode #2102
Closed
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.
Stack from ghstack (oldest at bottom):
Derived classes of
OpNode
are currently used only for prepack or execute, never both. This means they need not have both API.Inspired by Stephen's comment, we will build on
ExecuteNode
to be initialized with member functions forcreate_params_block()
,get_shader()
, etc.PrepackNode
doesn't need these members. Hence, it makes sense to separate the classes.Feel free to suggest better names. I don't really like mine.
Differential Revision: D54042646