Kent Fredric
Kent Fredric
Its because if you simply extend the normal interface, you're stuck, because the existing interface autoloads, and you can _either_ autoload, or use elective design, not both. Thus, the consumer...
I would have prerferred to use a role here actually, but I was trying to stay within the existing design approaches in the codebase. If the codebase was amenable to...
As a linux vendor packager, I'm somewhat fond of the "handle these binary assets in a seperate crate" idea, just i know you'll have to exercise some kind of discipline...
Oh hai @chewi, fancy seeing you here. Just reporting that under cross compile, the built perl still segfaults this way w/ perl 5.30.3 w/ cross 1.3.4 & GCC 10. This...
( NB: in case you wonder why the checksum changed, the first one was built with --features 'seccomp', and the second was with an added --no-default-features *just* in case std...
Also worth mentioning that its a single test breakage causing this. Which is fortunately easy to gate out vendor-side. But just as worthy of mentioning, the omitted data dir is...
When you have errors like this, use some tool like Devel::Confess to get a more comprehensive stack trace, including context and arguments. Also, don't screenshot errors, that's the _least useful_...
Would probably be worth having an ability to reduce results down to those in a given backend/ecosystem by name in the API. For instance, I want to make a suggestion...
For me, this background was important data for consideration in regards to "naming". Because unless you *do* have a strict adherence somewhere in your data to both identify: 1. The...