Front page | perl.perl5.porters |
Postings from January 2022
On Tue, Jan 25, 2022 at 7:57 PM Tom Molesworth via perl5-porters < perl5-porters@perl.org> wrote: > On Wed, 26 Jan 2022 at 07:54, Scott Baker <scott@perturb.org> wrote: > >> I love both of these suggestions. Let me put on my Perl novice hat and >> respond directly: >> >> 1. >> >> One of my favorite things about git is that when something is wrong >> with your working state, or you issue an incorrect command, git tells >> you not only that there is an error, but also what the most likely fix is. >> This has saved me numerous times from having to stop what Iâm doing and >> Google the specific error. Simple one line errors suggestions like that can >> save a lot of time and frustrations. >> >> indeed - and there's precedent for this in the `(you may need to install > the XYZ module)` error shown when trying to use/require a module that isn't > found. > > RFC seems unnecessary for this - might as well go straight for the Github > pull request? As long as the extra text goes at the end of the warning, the > change does not seem overly controversial! > I would like to give the wording a few passes, and the interesting bit will be how it updates the perldiag entries, but agreed that this seems a good idea and does not need an RFC. -DanThread Previous