We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The text was updated successfully, but these errors were encountered:
K stride is decided before hand so the cost model can consider it but not really Is the polynomial eval just going away now?
Sorry, something went wrong.
Yes, poly eval is goooooone. Because when we merge tables it doesn't make sense to have it.
ecmargo
jkwoods
No branches or pull requests
The text was updated successfully, but these errors were encountered: