Windows Defender identifies proc-macro-hack dependency artifacts as a threat

[ErichDonGubler]

Unfortunately, Windows has started identifying compilation artifacts from phf on my machine as a threat; this is because at least one proc-macro-hack artifact in the user's Temp folder are is identified as a threat:

Because the MSRV of this crate is 1.46, and upstream proc-macro-hack's repo README.md states:

Note: As of Rust 1.45 this crate is superseded by native support for #[proc_macro] in expression position. Only consider using this crate if you care about supporting compilers between 1.31 and 1.45.

...my conclusion is that phf and phf_macros should shed their proc-macro-hack dependencies as the best way to resolve this issue. Will file a PR shortly for this, as migration is a light lift.

---

Additional info:

• Reproduced using an unmodified commit a3e04bc.
• More rigorous repro steps and environment info can be found at Windows Defender identifies proc-macro-hack's transitive dependency artifacts as a threat Ogeon/palette#289, where I've filed an issue against palette as a consumer of this crate.