- if private declaration has annotations, it's considered as used to avoid costly implicit usages checks
- even private companion objects are now considered as used
- operators are ignored as well
GitOrigin-RevId: 069d245017438574ddfb73df764d01fa360c688b
- Add separate option to enable/disable this inspection, as it is not
obvious if it should be always enabled or not
- This option can be used to detect all unnecessary qualifiers in
tests
- Add possibility to configure inspections via `settings.xml` in the
`AbstractMultiFileLocalInspectionTest.kt`
- ^KT-18538 Fixed
Original commit: 7fb5acc718f8e53eb2e6b5d9dadd2efb64e7b588
GitOrigin-RevId: 92b6c127d93c469907e62c485b0d8943d5fa7c23
Generation of inline classes is quite complicated: we mangle methods,
add stubs and synthesized methods. So, for simplicity, to avoid
logic duplication in dummy resolve and in the backend, currently we
will use only the latter for light classes generation
#KT-26843 Fixed
GitOrigin-RevId: 341b20f048275a51644c82c8d0354601e391227b
Before this commit, sealed sub-class without state was considered
a style issue.
After this commit, sealed sub-class without state AND custom equals
is considered a probable bug,
because comparison of its instances is very fragile.
Alternative fix (generate equals & hashCode by identity) is added.
GitOrigin-RevId: c8303a815b56cfb1643c9a9c2804ac1b2d5354db
Bart van Helvert
Alexander.Danilov
Roman Golyshev
Anna Kozlova
Frederik HaselmeierandMichail Zarečenskij
Jaebaek Seo
Alexey Belkov
Toshiaki Kameyama
Dmitry Gridin
Mikhail Glukhikh
Gabryel Monteiro