Not to throw shade, just wishing that somebody here can understand. Whenever an input is reasonably long, an analyzing function will crash, and this PR aims to fix that with a mechanism that contradicts the maintainer’s understanding while a similar C implementation does not need this fix. Clearly, the maintainer has not heard a certain programming mantra…

  • jwaters42@beehaw.org
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    After the xz debacle, I think we should resist the temptation to rush maintainers into accepting code that they don’t fully understand.

      • towerful@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        7 months ago

        No you aren’t.
        The title is demeaning.
        “don’t want to throw shade” as if we all know what’s going on except the people involved in the link.
        “Clearly the maintainer hasn’t heard of a certain…” Haha, we are in the same group, right? We know what’s up, guys… Right? Haha, look at these losers.

        Never mind that you are applying a time pressure on open source maintainers to try and merge a change they don’t understand. Not very respectful. And quite frankly, in extremely bad taste considering the recently revealed xz social engineering.

        Where is the question?
        There isn’t a single question mark in your post. You frame it as if their problem and they don’t understand.
        Even here, where you are so close to asking, you make it sound like you are checking that everyone here understands.