uh-oh, I made clippy ICE 🤓 paste.rs/Dy5

trying to choose a method name… reset? clear? I type “fn clear” then check what Vec calls it :- “clear”. Yay :-)

kind of disappointed that i need the impl here and now i’m not sure if the supertrait is doing anything useful trait HeapLen: DnsName { fn heap_len(&self) -> usize { 1 + self.labs() + self.nlen() } } impl<T: DnsName> HeapLen for T {}

the answer is that the supertrait is bringing the necessary methods into scope in the other case where i had a default function implementation, the methods it called were in the same trait

repeatedly trying to #[macro_use] a module and invoke one of its macros, and yet rustc insists the macro is not visible and have I forgotten to #[macro_use]?

macro_rules is annoyingly parse-order scoped rather than lexically scoped. make sure your macro is *before* its use in your codebase's parse order.

oh yeah now i remember took me an age to work it out last time :-/

maybe i should always declare all my submodules at the bottom :-)

Or all your macros in a macros.rs and `#[macro_use] pub mod macros` at the top :D

heh, except this macro is an implementation detail to abbreviate some common trait impls