Forbidden bitwise operation Open
IMAPS = 1 << 13,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
SFTP = 1 << 5,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
RTMPTE = 1 << 22,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
FILE = 1 << 10,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
POP3 = 1 << 14,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
RTMPE = 1 << 21,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
HTTPS = 1 << 1,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
RTSP = 1 << 18,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
MQTT = 1 << 28,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
RTMPT = 1 << 20,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
GOPHERS = 1 << 29,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
LDAPS = 1 << 8,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
POP3S = 1 << 15,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
SMTP = 1 << 16,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
RTMPTS = 1 << 24,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
LDAP = 1 << 7,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
DICT = 1 << 9,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
SMBS = 1 << 27,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
HTTP = 1 << 0,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
ALL = ~0,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
SCP = 1 << 4,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
TELNET = 1 << 6,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
RTMPS = 1 << 23,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
FTPS = 1 << 3,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
TFTP = 1 << 11,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
FTP = 1 << 2,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
GOPHER = 1 << 25,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
SMB = 1 << 26,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
IMAP = 1 << 12,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
SMTPS = 1 << 17,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.
Forbidden bitwise operation Open
RTMP = 1 << 19,
- Read upRead up
- Exclude checks
Rule: no-bitwise
Disallows bitwise operators.
Specifically, the following bitwise operators are banned:
&
, &=
, |
, |=
,
^
, ^=
, <<
, <<=
,
>>
, >>=
, >>>
, >>>=
, and ~
.
This rule does not ban the use of &
and |
for intersection and union types.
Rationale
Bitwise operators are often typos - for example bool1 & bool2
instead of bool1 && bool2
.
They also can be an indicator of overly clever code which decreases maintainability.
Config
Not configurable.
Examples
"no-bitwise": true
For more information see this page.