In this particular case it means you cannot write web scrapers using rakudo. And not only that, but it makes you feel like rakudo is completely broken if it can't even go through a few tens of pages without SEGV-ing. If Skarsnik's suspicion that the issue is in XML right, then it's not just with gumbo but with any module using XML module for serious work.
Not all bugs are annoying. Anything that errors out during the compilation is not [ANNOYING] because the issue just jumps right at you. Anything that has a workaround is probably not [ANNOYING] because there's a way to deal with the issue. For example, in this case: * It doesn't SEGV for the first few pages you scrape, so before you know about this ticket you'll probably proceed with whatever you're doing… and in the end when you start doing your almost-production runs you'll realize that it doesn't work and it won't work ever, no matter what you do because… * There's no reasonable workaround. The only thing I've come up with is using python-gumbo through Inline::Python so that's what I am doing sometimes. It's horrible. And yes you'll have to rewrite the whole thing. I've introduced the [ANNOYING] tag very recently, so there's no comprehensive list yet. But take a look at https://fail.rakudo.party/t/ANNOYING for some examples. Most of these create “rakudo sucks” impression and have no reasonable workarounds. But I haven't thought about the actual criteria yet. On 2017-10-04 12:38:26, sml...@gmail.com wrote: > What is the point of the `[ANNOYING]` tag? > All bugs are probably annoying to *someone*...
