Re:The problem with Go’s default HTTP handlers
by scriptsmith on Tuesday August 09, 2022 @09:55PM
(#32407068)
Thank you! I ran into this branching problem the other day, ended up trying to return a complicated boxed future and gave up.
In retrospect it makes sense to do it the way you mentioned. I think because I’m not as confident with traits and rust’s brand of async I tried to get it to work the same way I would in other languages, which is to mess with the function’s return type myself, rather than let the compiler figure it out.
In retrospect it makes sense to do it the way you mentioned. I think because I’m not as confident with traits and rust’s brand of async I tried to get it to work the same way I would in other languages, which is to mess with the function’s return type myself, rather than let the compiler figure it out.