Require a route to respond with a status about rho

[arouel]

Do we have an example what flexibility we loose in the route definition?

[bryce-anderson]

We would lose the ability to do

route |>> { () => "foo" }

and would instead require

route |>> { () => OK("foo") }

but wouldn't lose the ability to send any particular types. It would end up
limiting the reuse of functions as I can see things of the form being
hindered:

def foo(): String =??
route |>> foo

[arouel]

Okay, understand! I think this is a really good idea and leads to a more explicit response definition that is really valuable.

[bryce-anderson]

Alright, when I get some time I'll branch and see what I can do. If you want to get at it, just post a message here so I don't duplicate your effort.

[bryce-anderson]

I've made a branch to start feeling it out. Some notes.

• Pretty much non of the http4s core EntityResponseGenerator stuff can be reused and may be confusing
• Reverse routing is less useful, but not dramatically so
• We can eliminate the ObjToResponse stuff and the burden gets moved to the HListToFunc

I don't like how much we lose, but I think its a requirement to be able to return different statuses so I think this might be the way to go. I'd love to hear other opinions.