in reply to Endorsement from committer to submit TPF Grant Application to add given/when to Switch.pm

The problem with given/when is that the design is broken. How do you plan to modify it to address this?

  • Comment on Re: Endorsement from committer to submit TPF Grant Application to add given/when to Switch.pm

Replies are listed 'Best First'.
Re^2: Endorsement from committer to submit TPF Grant Application to add given/when to Switch.pm
by jeffenstein (Hermit) on Apr 02, 2024 at 08:11 UTC
Re^2: Endorsement from committer to submit TPF Grant Application to add given/when to Switch.pm
by ait (Hermit) on Apr 01, 2024 at 14:34 UTC

    I don't have an answer for this at the moment which is why I proposed 40 hours of work to analyze the current implementation, look at the Raku implementation and then come up with simplified design that covers most of the cases people have been using given/when for in Perl 5

    Also, in the grant proposal I stated that the most qualified person for this is probably Switch.pm author, but perhaps some other qualified volunteer is able and willing to do it.

    I would volunteer but not before fully understanding the flaws of the current design, perhaps something we can hash out in this thread at least. I have personally used given/when in it's simple full match form, easily replaceable by if ($foo eq 'bar') elsif, elsif, else. But maybe a lot of people used the advanced smart matching which is where I believe the current implementation is flawed. But I am not sure, because I never used any of these advanced features of given/when and I suspect most people didn't either.

    Maybe we should also hold a poll to see if people used given/when for more than just a simple matching switch.

      I asked because it sounded like you wanted a drop in replacement for given/when ("allow most people to simply replace use feature 'switch' by use Switch").