c5c0cbccde
Redundant companion reference: simplify name conflict checking code
...
Before this commit, function with same name but different signature
wasn't counted as name conflict, now it is - just because that exact
check in this place could be too complex and error-prone
Enhancement for KT-27539
2018-11-29 14:32:08 +03:00
1db7a0e0cc
Redundant companion reference: don't report in case of name conflicts
...
#KT-27539 Fixed
2018-11-29 14:32:08 +03:00
23b9889ebb
Redundant companion reference: Fix false negative in enum entry #KT-27861 Fixed
2018-11-07 17:21:41 +03:00
d0d98dc283
Redundant companion reference: fix false positive for class with name Companion #KT-27861 Fixed
2018-11-07 11:53:22 +03:00
7a9effe30d
Redundant companion reference: Fix false positive in enum entry #KT-27861 Fixed
2018-11-06 11:02:35 +03:00
5ad98a139d
"Redundant Companion": Don't suggest if same callable name is in use
...
So #KT-24425 Fixed
2018-06-19 12:48:10 +03:00
a5aad22fe7
Don't report "Redundant Companion reference" on accessing nested object
...
So #KT-23620 Fixed
2018-04-11 17:00:37 +03:00
ab973b2ff0
Fix several false positives and make safer "redundant companion ref"
...
Don't report it on an import directive #KT-23520 Fixed
Don't report it if companion nested class is referenced #KT-23519 Fixed
Check companion reference both by descriptor and by name
2018-04-03 17:45:14 +03:00
e96b5f3117
Fix false positive in redundant companion reference #KT-23435 Fixed
2018-03-28 13:27:45 +02:00
3fbf85dc37
Add inspection to highlight unnecessary explicit companion references
...
So #KT-22971 Fixed
2018-03-21 09:15:48 +03:00
Mikhail Glukhikh