in reply to What modules should be added to the corelist?

CGI, of course! :-p

Joking aside, the modules I consistently seem to have to deploy everywhere include Try::Tiny, Log::Any and LWP::Protocol::https (update: and Ref::Util). But it's not like any of these are massive or tricky to install so I don't really see a need to bloat corelist at all.

  • Comment on Re: What modules should be added to the corelist?

Replies are listed 'Best First'.
Re^2: What modules should be added to the corelist?
by Anonymous Monk on Aug 16, 2019 at 14:26 UTC
    I would rather see Syntax::Keyword::Try in core. The corollary to that is that it would make sense as a feature flag, and as a core feature it could reach into internals that a CPAN module cannot (unless you're Coro).
[reply]
      ...then I guess you'll be happy to know that it was a core feature 3 years ago, and as of v5.40, it is no longer experimental. 

      $ perl -E 'use v5.40; try { die "x" } catch ($e) { say $e; }'

      [download]
[reply]
[d/l]

        yes indeedee I discovered this a few weeks ago. OT: I sometimes used Try::Tiny. Do you know how the name clash will be handled if I don't modify my code to remove that package?

[reply]

In Section Meditations