This doesn't prevent code compilation but is definitely quite annoying. Adding the unsafe keyword to my module function definition doesn't solve the problem, because (I suspect) the underlying macro produces output that doesn't have the unsafe keyword.
I see the following when I expand the map proc macro:
When using params as the first argument to a map module, clippy will report:
This doesn't prevent code compilation but is definitely quite annoying. Adding the
unsafe
keyword to my module function definition doesn't solve the problem, because (I suspect) the underlying macro produces output that doesn't have theunsafe
keyword.I see the following when I expand the
map
proc macro:which indeed contains some unsafe code.