Sometimes a new question was in fact a duplicate and should be closed as such. But in the quest to close duplicates I pretty frequently had to argue with the reviewer that "No, this isn't a duplicate just because these two questions related to the same library".
SO practically rewarded this sort of over-policing which I think is a big part of why everyone stopped using it.
And people stopping using it meant that when a question did actually make it through the gauntlet, it was likely to go unanswered because everyone who knew anything had left the platform.
Please show examples. People arguing that XYZ is not a duplicate made up a large fraction of volume on the meta site, and in the overwhelming majority of cases it was very clear that the question was indeed a duplicate per site policy. It absolutely was not something people would do "just because these two questions related to the same library". (If it were really like that, tags would never get more than one question each.)
The goal is not that you can copy and paste code from the answer and have it work as-is. Minimally, we don't know your variable names, constants etc. and any number of other trivial details like that which perhaps shape the problem you are facing but are completely irrelevant to the question.
I'm not going to go dig through SO to refind the examples of improperly "closed as duplicate" questions I stumbled on years ago while looking up a problem.
It's just not that important to me for a dead site. I get it, that means "just trust me bro" is in play. Feel free to completely ignore my comment in that case. You win.
SO was filled with this sort of "technically this is a duplicate and you are just a nasty rule breaker" style comments with litigation that ultimately goes nowhere. I'm not on SO.
Others experienced and are reporting here and elsewhere experiencing the harsh moderation of SO. Trying to make that subjective feeling technically wrong does nothing to rehabilitate SO's reputation.