also the point about clippy having a million warnings is just inaccurate: this is a Deny warning in clippy! this will fail your clippy build and will be red in the error list. perhaps it should be uplifted to rustc, but it's not bucketed the same way
Even if the function is declared as taking a pointer, references implicitly coerce, so it's rather moot what the decl uses IMO
-
-
Er, to clarify my tweet, my problem is not with using &, it's that the type being taken is fundamentally a pointer to a list of chars, not just one, and it would be nicer if a separate type existed for that, the way we have c_void
-
would
@oli_obk's procedural vtable RFC address this? - 17 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.