I love case/when menus, so I am all for suggestions that make case/when more
useful, so I also support this (even if this one is indirect, on class Hash,
to have them behave like a case/when menu).

I also would like to see case/when become first-class citizens (objects) one day
that can also be merged together (e. g. unify two different case/when menus
together, both working on the same variable... a bit similar as to how hashes
can be merged together too. A bit like UnboundMethod where we could, in
theory, detach a method and attach it to another object or use another
environment ... but I digress again, sorry.)

The name "fetch_as_in_case_construction" is indeed a bit terrible,
I am glad that I am not the only one who suggests terrible names. :D

But I think the more important part is whether matz/ruby core team
think that the underlying functionality would be ok to be had.

Finding good names is hard but possible! I also have no really better
suggestion. My suggestions may even be worse ... such as :)

Obvious ones would be ".to_case" or, if the other way around, on
a first-class citizen case object, .to_hash. Or some method called
"convert" or "transform" or "treat_as_case" or ... I dunno.

But +1 anyway.

Tsuyoshi Sawada wrote:

The name fetch_as_in_case_construction is terrible. Perhaps someone can suggest a better name.

What about simplifying this to fetch_as_case? Or maybe even just case? Just thinking out loud.

h.find {|a,| a === "barbar" }.last #=> "BAR"

This is good enough to me.

Yusuke Endoh wrote:

h.find {|a,| a === "barbar" }.last #=> "BAR"

This is good enough to me.

I expected something that would be as easy as and comparable to h[key].