https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.85.1 2024-12-26T14:15:54+00:00 2024-12-26T14:15:54+00:00 Philipp Krones hello@philkrones.com 2024-12-26T14:01:07+00:00 urn:sha1:8a7d8ece322d2ecd106f7c650a35ed8df777e109 2024-09-13T11:10:56+00:00 Obei Sideg obei.sideg@gmail.com 2024-08-24T03:49:09+00:00 urn:sha1:3b0ce1bc33d30d7d116ee9af60df873e04bd74dc 2024-01-11T16:27:03+00:00 Philipp Krones hello@philkrones.com 2024-01-11T16:27:03+00:00 urn:sha1:af39354819053122be87a21a9e13b1d5d8243151 2023-09-25T09:28:58+00:00 Philipp Krones hello@philkrones.com 2023-09-25T09:28:58+00:00 urn:sha1:3112e373aca4250d1444957ab4ded626cb99ee91 2023-08-24T19:32:12+00:00 Philipp Krones hello@philkrones.com 2023-08-24T19:32:12+00:00 urn:sha1:7137a09806171e75b54c5fb70bf629a55ff04d8b 2023-08-17T16:06:36+00:00 bors bors@rust-lang.org 2023-08-17T14:41:46+00:00 urn:sha1:09d05c04da516d4f54ccf41e22b544bc8c425373 [`useless_conversion`]: only lint on paths to fn items and fix FP in macro Fixes #11065 (which is actually two issues: an ICE and a false positive) It now makes sure that the function call path points to a function-like item (and not e.g. a `const` like in the linked issue), so that calling `TyCtxt::fn_sig` later in the lint does not ICE (fixes https://github.com/rust-lang/rust-clippy/issues/11065#issuecomment-1616836099). It *also* makes sure that the expression is not part of a macro call (fixes https://github.com/rust-lang/rust-clippy/issues/11065#issuecomment-1616919639). ~~I'm not sure if there's a better way to check this other than to walk the parent expr chain and see if any of them are expansions.~~ (edit: it doesn't do this anymore) changelog: [`useless_conversion`]: fix ICE when call receiver is a non-fn item changelog: [`useless_conversion`]: don't lint if argument is a macro argument (fixes a FP) r? `@llogiq` (reviewed #10814, which introduced these issues) 2023-07-02T12:59:02+00:00 Philipp Krones hello@philkrones.com 2023-07-02T12:35:19+00:00 urn:sha1:beb0e731de1c13ee0ee341965718b6350a48b34d 2023-05-20T13:39:26+00:00 Philipp Krones hello@philkrones.com 2023-05-20T13:39:26+00:00 urn:sha1:12cbb6ced8a848d1de68e7f0fe842217b9563ccc 2023-04-23T11:28:56+00:00 Philipp Krones hello@philkrones.com 2023-04-23T11:03:09+00:00 urn:sha1:4beb0a4bdf4c9547b00db232deab74406873d305 2022-12-29T13:28:34+00:00 Philipp Krones hello@philkrones.com 2022-12-29T13:28:34+00:00 urn:sha1:56ab392f028b1d5dab1c2eb2e4af37136915882c