-
Notifications
You must be signed in to change notification settings - Fork 17
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
Compile time optimizations #134
Conversation
@@ -238,6 +238,20 @@ bool OpBase_IsWriter | |||
return op->writer; | |||
} | |||
|
|||
// indicates if the operation is an eager operation | |||
bool OpBase_IsEager |
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.
there is already one like this called ExecutionPlan_isEager
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.
A bit confusing but ExecutionPlan_isEager
checks to see if the Execution-Plan spanned from the given root contains an eager operation while OpBase_IsEager
checks if the given operation is an eager op.
Seperate execution plan optimisations into compile time optimizations and runtime optimizations
Compile time optimizations are cached.
Compile time optimizations:
Runtime optimizations: