Ottavio Hartman 111bbc61f6 [refurb] New rule to suggest min/max over sorted() (FURB192) (#10868) ... ## Summary Fixes #10463 Add `FURB192` which detects violations like this: ```python # Bad a = sorted(l)[0] # Good a = min(l) ``` There is a caveat that @Skylion007 has pointed out, which is that violations with `reverse=True` technically aren't compatible with this change, in the edge case where the unstable behavior is intended. For example: ```python from operator import itemgetter data = [('red', 1), ('blue', 1), ('red', 2), ('blue', 2)] min(data, key=itemgetter(0)) # ('blue', 1) sorted(data, key=itemgetter(0))[0] # ('blue', 1) sorted(data, key=itemgetter(0), reverse=True)[-1] # ('blue, 2') ``` This seems like a rare edge case, but I can make the `reverse=True` fixes unsafe if that's best. ## Test Plan This is unit tested. ## References https://github.com/dosisod/refurb/pull/333/files --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>		2024-04-23 01:13:57 +00:00
..
test	[refurb] New rule to suggest min/max over sorted() (FURB192) (#10868)	2024-04-23 01:13:57 +00:00
__init__.py	[pylint] (Re-)Implement import-private-name (C2701) (#9553)	2024-01-16 14:03:11 -05:00