You're right, it doesn't really seem necessary and makes the responses of the route end up as side effects rather than part of the return type of the route func

You're right, it doesn't really seem necessary and makes the responses of the route end up as side effects rather than part of the return type of the route functions. Most web frameworks in Rust don't make responses a side effect and keep them as a response return type since that's better devex and much less boilerplate.