Incorporating functions in Rust lang/prelude with clashing function name with a dependency crate in cargo toml

I have some suggestions as to how to go about incorporating functions with the same function name as that of a dependency crate in order to prevent conflicts.

rust-lang/rust#79524 has inspired me to create this RFC.

My suggestion goes something like this:

1. Add a flag to Cargo.toml to load std functions before dependency functions which is by default added for new rust versions (personally I would want to include it as a feature of a new Rust edition, but since 2021 got released just now I am not so sure) even if the user declares to use the dependency crate globally unless the user marks it as something like !important or priority use
2. If there is a function with the same name in the std lib as that of dependency, and if the stdlib function is used clippy should show a warning. Needless to say if any error occurs while compiling, proper source of the function should be made evident in the error messages.
3. All of this is not required if the dependency crate is not called upon in the Cargo.toml

Start by reading rust-lang/rust#79524 and the proposed behavior in this issue. Define how Cargo.toml dependency declarations, standard-library name precedence, clippy warnings, and compiler diagnostics should interact. Done means the proposal has a settled, implementable design with clear behavior when the dependency is absent.