#to_a — Public Fediverse posts

Have you ever wondered why Ruby has both #to_i and #to_int methods? Or both #to_a and #to_ary? In today's episode we'll answer this question, and look at how we can use implicit conversion methods to our advantage.

https://graceful.dev/courses/tapastry/modules/2014/topic/episode-210-implicit-conversion/

Have you ever wondered why Ruby has both #to_i and #to_int methods? Or both #to_a and #to_ary? In today's episode we'll answer this question, and look at how we can use implicit conversion methods to our advantage.

https://graceful.dev/courses/tapastry/modules/2014/topic/episode-210-implicit-conversion/

@cllns I know that Rack 3.0.0 will break how Server Sent Events work as middleware. It's not hard to fix but does require fixing by manually moving away from `#each` to `#to_a` for example.

I guess this means that Hanami 2.3.0 will still default to Rack 2.2.x but switch to Rack 3.0.0 if detected in the gem file?

@cllns I know that Rack 3.0.0 will break how Server Sent Events work as middleware. It's not hard to fix but does require fixing by manually moving away from `#each` to `#to_a` for example.

I guess this means that Hanami 2.3.0 will still default to Rack 2.2.x but switch to Rack 3.0.0 if detected in the gem file?