You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2024. It is now read-only.
Pylint’s sole argument seems to be performance, which to me seems a clear case of premature optimization. The issue that introduced the checks, pylint-dev/pylint#4365, contains no reasoning at all, just the assertion that the literals would be “would be clearer”.
I like list() and dict() and set() and tuple() better myself for empty collections. Let’s enforce that instead.
The text was updated successfully, but these errors were encountered:
Split from #1860. Pylint:
charliecloud/lib/build.py
Line 334 in d679373
Pylint’s sole argument seems to be performance, which to me seems a clear case of premature optimization. The issue that introduced the checks, pylint-dev/pylint#4365, contains no reasoning at all, just the assertion that the literals would be “would be clearer”.
I like
list()
anddict()
andset()
andtuple()
better myself for empty collections. Let’s enforce that instead.The text was updated successfully, but these errors were encountered: