You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to add disallowed-methods to a clippy.toml in a workspace. The workspace uses multiple versions of a dependency, and an API path changed between the versions, so the resulting TOML looks similar to this:
disallowed-methods = [
{ path = "foo::Bar::baz" }, # crate foo v1 exports Bar at the crate root
{ path = "foo::bar::Bar::baz" }, # crate foo v2 exports Bar from the bar module
]
This generates warnings on one of the items, usually the newer version
`foo::bar::Bar::baz` does not refer to a reachable function
The workaround is to add allow-invalid = true, but this means I don't get the warning if I did accidentally write the wrong path.
How do I write the fully qualified path for foo@1::Bar::baz and foo@2::bar::Bar::baz such that Clippy understands without allow-invalid = true?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to add disallowed-methods to a clippy.toml in a workspace. The workspace uses multiple versions of a dependency, and an API path changed between the versions, so the resulting TOML looks similar to this:
This generates warnings on one of the items, usually the newer version
The workaround is to add
allow-invalid = true, but this means I don't get the warning if I did accidentally write the wrong path.How do I write the fully qualified path for
foo@1::Bar::bazandfoo@2::bar::Bar::bazsuch that Clippy understands withoutallow-invalid = true?Beta Was this translation helpful? Give feedback.
All reactions