Remove `log` renamings of `tracing` crate

[oli-obk]

In #74726 I made a dependency import hack to reduce the diff size. We should replace all of these imports with tracing = "0.1" and then adjust the crate source by replacing all uses of log imports with tracing import.

Ideally only a few of these are done at a time to keep conflicts at a minimum and get such PRs merged fast.

Note: do not start working on this until #74726 is merged.

• librustc_ast
• librustc_ast_lowering
• librustc_ast_passes
• librustc_ast_pretty
• librustc_builtin_macros
• librustc_codegen_llvm
• librustc_codegen_ssa
• librustc_data_structures
• librustc_driver
• librustc_errors
• librustc_expand
• librustc_hir
• librustc_incremental
• librustc_infer
• librustc_interface
• librustc_lint
• librustc_metadata
• librustc_middle
• librustc_mir
• librustc_mir_build
• librustc_parse
• librustc_passes
• librustc_privacy
• librustc_query_system
• librustc_resolve
• librustc_save_analysis
• librustc_session
• librustc_span
• librustc_symbol_mangling
• librustc_target
• librustc_trait_selection
• librustc_traits
• librustc_ty
• librustc_typeck
• compiletest
• librustdoc

[bishtpawan]

Hi @oli-obk I saw your PR of (#74726 ) where you have replaced log="0.4" to log = { package = "tracing", version = "0.1" } and in this issue, you have mentioned like we have to replace all log imports to tracing imports. My question here is when you have already changed the package from log to tracing so now what left in it because the import name cannot be changed in files if we have used log as a crate name in Cargo.toml?
Do we need to replace the name of dependency from log to tracing then we'll clean up the code by replacing the log imports with tracing imports in the corresponding files? Or is there anything else you want?

Thanks,
Waiting for your response.

[oli-obk]

Do we need to replace the name of dependency from log to tracing then we'll clean up the code by replacing the log imports with tracing imports in the corresponding files? Or is there anything else you want?

Yes, that's exactly it. Replace log = { package = "tracing", version = "0.1" } with tracing = "0.1" and then fix up the errors by changing the import names. Note that the PR isn't merged yet, so this issue is not yet actionable.

[bishtpawan]

Thanks for the response. Yes, I'm waiting for your PR to be merged first.

[georgio]

I would like to give this a shot when #74726 is merged

[oli-obk]

Once the PR is merged, before you work on anything, please post here which libs you are going to work on so that you don't conflict with others who are doing the same

[pawanbisht62]

As they are independent, we can make changes on multiple files right? If yes then I'll work on following libs

• librustc_ast_lowering
• librustc_ast_passes
• librustc_ast_pretty
• librustc_builtin_macros
• librustc_codegen_llvm
• librustc_codegen_ssa
• librustc_data_structures)
  After that will pick new libs accordingly if we will left with some.
  Thanks

[gdhuper]

If no one else is planning on tackling the following:

• librustc_session
• librustc_span
• librustc_symbol_mangling
• librustc_target
• librustc_trait_selection
• librustc_traits
• librustc_ty
• librustc_typeck
• compiletest
  I would like to take a stab. Thanks

[georgio]

I could take care of the remaining files:

• librustc_ast
• librustc_data_structures
• librustc_driver
• librustc_errors
• librustc_expand
• librustc_hir
• librustc_incremental
• librustc_infer
• librustc_interface
• librustc_lint
• librustc_metadata
• librustc_middle
• librustc_mir
• librustc_mir_build
• librustc_parse
• librustc_passes
• librustc_privacy
• librustc_query_system
• librustc_resolve
• librustc_save_analysis