Conversation
7be1f73 to
cf3cb4b
Compare
|
"Simplify log macro setup" tries to make the log shim in this crate more like rustls', but so far I can't quite get it to work. As reported by CI, error[E0433]: failed to resolve: could not find `warn` in `log`
--> src/config.rs:61:25
|
61 | crate::log::warn!("native root CA certificate loading errors: {errors:?}");
| ^^^^ could not find `warn` in `log`(Not sure what's different about these crates? What am I missing?) If I skip that commit, I get this error: error[E0659]: `warn` is ambiguous
--> src/lib.rs:59:20
|
59 | pub(crate) use warn;
| ^^^^ ambiguous name
|
= note: ambiguous because of a name conflict with a builtin attribute
= note: `warn` could refer to a built-in attribute
note: `warn` could also refer to the macro defined here
--> src/lib.rs:57:5
|
57 | macro_rules! warn ( ($($tt:tt)*) => {{}} );
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^If someone else wants to take a look, that would be great! |
I never got this to work as desired in rustls, though I think I now understand more about how macro visibility works. Over there it works in a weird way:
in the first case, the pushed a commit which avoids all that by keeping the macros local, and explicitly if that looks good i'll squash it into your earlier commit? |
1d0aba6 to
bf8efc3
Compare
|
Awesome, thanks! I took care of the squashing. |
bf8efc3 to
607676c
Compare
607676c to
2e25331
Compare
Oops, took that commit out. |
Didn't call anything out in the release notes since it's just a grab bag of smaller stuff. |
No description provided.