Obviate typespec_client_core dependency in generated code #2382
Labels
Azure.Core
The azure_core crate
Client
This issue points to a problem in the data-plane of the library.
Milestone
As mentioned in Azure/typespec-rust#324, we couldn't get rid of the
typespec_client_core
dependency in generated crates'Cargo.toml
files because of a couple derive procedural macros.The
Model
derive macro does already have a solution where we can change the crate referenced used:But it looks like the
SafeDebug
derive macro would need the same capability, or find a way to avoid even referencing thetypespec_client_core
crate. The only reason it does currently is because it actually implements thetypespec_client_core::fmt::SafeDebug
trait in addition tostd::fmt::Debug
:We probably don't even need that trait. I didn't have specific plans for it. The main goal was to safely implement
std::fmt::Debug
but figured a separate trait could factor into issues regarding sanitization.See https://github.com/Azure/typespec-rust/pull/324#discussion_r2010755513 for context
The text was updated successfully, but these errors were encountered: