Closed ALSchwalm closed 6 years ago
Thanks for the fix!
However I don't really understand why the macro would use the Result
from the enclosing scope. (This is not a criticism of your PR, I really don't understand).
I believe it's because the macro expands to use the type Result
when it should instead use the full path ::std::result::Result
in case the Result
type in scope has been aliased to something else. So instead of use std::result::Result
, the usages of Result
in the macro should be changed to the fully qualified path, ::std::result::Result
.
Ah yeah. Sorry, I derped. Thanks!
Currently
post_input
does not explicitly usestd::result
. Instead, it uses theResult
from the enclosing scope. As projects will frequently define their ownResult
type, this can result in some cryptic errors like in #156. I didn't immediatly see anywhere else this could be a problem in rouille, but let me know if there are any other places and I can add them to this PR.