-
Notifications
You must be signed in to change notification settings - Fork 153
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
Kill PerformanceWarning #2348
Comments
As discussed in the fornightly, a good solution is not yet found. The use of print-statements worsens the spam to the console, which in general opinion should be prohibited. Other discussed options were the use of a logging infrastructure or mentioning the warnings in comments or in a separate file, but this is very easy to ignore. For further discussion a separate meeting is planned. |
As discussed in the fortnightly, the PerformanceWarnings have no clear semantics. Who is warned about what? Right now, they look like glorified TODO comments. Remove them and replace them with either TODO comments or explicit prints (especially in the TPC-C binary).
The text was updated successfully, but these errors were encountered: