Stephen Celis

> Your benchmarks suggest it could be faster: [...snip...] I think @davidcelis was working on getting updated benchmarks as there was some variation. The routing is predominantly handled by rack-mount,...

> A proper divide between the slimist of crepe and the "basic usage case" of crepe. Right now I'm using crepe as a router and I love it for that....

Anyway, my short list of things to look into before 0.9.0: - **Audit rendering.** Have we covered our bases here? Should we simplify? Some of our "smart" helpers like the...

> My issues with Crepe::Params have, interestingly enough, been with them being frozen (e.g. https://github.com/goodbrews/api/blob/master/app/apis/users_api.rb#L61-L71). I tried various forms of dup and clone to get a params hash I could...

:+1: We're getting there.

> Rendering and request body parsing could have closer looks taken at them at this point. An update: Rendering I think it pretty bare-bones and flexible at this point. I...

Also would love some discussion around versioning, here: https://github.com/crepe/crepe/issues/56

One more issue warranting discussion: https://github.com/crepe/crepe/issues/57 I think that's basically it. Got a lot of good work done on Crepe the past couple weeks and I think we're close to...

I added this recently because Active Support doesn't even manage its own dependency loading very well (you can require HashWithIndifferentAccess but if you try to instantiate one with a nested...

@phausler Should I be opening these kinds of clock issues here or directly on Swift? It seems like the issues outlined above may be both issues with the `debounce` operator...