1^V:Қ d dl mZ d dlZd dlmZmZmZmZ d dlm Z d dl
mZmZ d dl
mZmZ d dlmZ erd dlmZ ej d k rd d
lmZ nd d
lmZ G d de ZddZdS ) )annotationsN)
TYPE_CHECKINGTupleTypecast)nodes)BaseCheckerutils)only_required_for_messages
safe_infer) INFERENCE)PyLinter)
) TypeGuardc ^ e Zd ZdZdZddddddd d
ifdZdd
ddddffZd.dZ ed d/d Z ed d0d Z
ed d1d Z ed d2d Zd/d!Z
d2d"Zed3d( Zed4d* Z ed d5d, Zd-S )6CodeStyleCheckeram Checkers that can improve code consistency.
As such they don't necessarily provide a performance benefit and
are often times opinionated.
Before adding another checker here, consider this:
1. Does the checker provide a clear benefit,
i.e. detect a common issue or improve performance
=> it should probably be part of the core checker classes
2. Is it something that would improve code consistency,
maybe because it's slightly better with regard to performance
and therefore preferred => this is the right place
3. Everything else should go into another extension
code_style)z