Deprecation warning only requires new code to use the new items, no date of removal has been added and the compiler essentially just optimises this away.
If a human had added this as part of a general refactor to improve readability and bring the entire codebase to a modern idiomatic Go place... then I'd consider it. But an automation that performs minor and unneeded changes is a reject from me.
Deprecation warning only requires new code to use the new items, no date of removal has been added and the compiler essentially just optimises this away.
If a human had added this as part of a general refactor to improve readability and bring the entire codebase to a modern idiomatic Go place... then I'd consider it. But an automation that performs minor and unneeded changes is a reject from me.