There is a dispute on whether or not this regex question should be closed as a duplicate.
My position is that the question is a duplicate. Both of the techniques posted as answers are found in the single answer posted by Wiktor at Regex match numbers not followed by a hyphen which I used when I voted to close. The OP didn't need the whole pattern to be supplied, only a fix for the end portion of the pattern.
The page has been: (Timeline)
Answered by @thefourthbird
Hammered by @WiktorStribiżew
UnHammered by @thefourthbird
Answered by @anubhava
Then two close votes are invalidated (I don't know how to read that part of the timeline)
Then I voted to close and requested a cv-pls in SOCVR saying:
cv-plsregex exact duplicate stackoverflow.com/q/66063316/2943403 (...okay, replace the hyphen with an opening parenthesis, otherwise identical.
Hammered by @tripleee
Unhammered by @anubhava
Then there is another review item listed (which I don't know how to read)
Closed as a duplicate by @Dharman, @TylerH, @Makyen♦
@Makyen♦ edited the dupe list and said:
IMO, this is a duplicate. The issue here is the same as the issue and solutions in the duplicates which have been used: backtracking permitting the match to backtrack a single character in order to not match a negative look-ahead. If we permit having individual questions for every single possible different character, character class, or group which might encounter the identical issue, then there are an infinite number of possible questions which are all about the same issue and which all share the same solutions. Doing that would seriously fragment where good answers can be found.
Then there was a split decision from the Reopen Review Queue (if I read that correctly) resulting in the page being re-opened.
Then @Makyen♦ re-hammered, adjusted the dupe list, and locked the page.
So where do we go from here? It seems to me that some camps want to ensure that only snowflake to snowflake identical questions are closed as duplicates. Whereas other volunteers want to see new pages closed where pre-existing advice can be applied to a new similar scenario.
I am in the latter camp. Highly skilled regex veterans are answering the same kinds of questions using the same techniques over and over. Stack Overflow is not meant to be a point farm that ignores old posts -- we should be endeavoring to honor past contributions by pointing new researchers to old questions when appropriate. We also need answerers to search the site just like we expect askers to search the site. With Stack Overflow already housing millions of pages, it is more likely than not that a new question is a duplicate -- certainly questions asking for narrow/basic techniques.
Should regex get special treatment because there are a lot of users who 1. Are new to regex, 2. Find regex impossibly mystifying 3. Don't want to spend the time to learn regex? I say: no special treatment. We should all want developers to be on a growth trajectory. We want researchers to immerse themselves in the supremely generous pool of knowledge that has been curated for over a decade by some very, very smart folks.
So where do we go from here? Are we going to try to condense and funnel the wisdom here by closing duplicates or are we going to answer every question that is even slightly different by a character or two and see a lot less cohesion in the content?
Should we be encouraging people to answer duplicates and then hammer the page closed so that we have more diverse "sign posts" to help direct pages? I can do that, but it doesn't feel "right". I find myself extremely irritated by the lack of official guidance on where Stack Overflow is meant to be headed. I am not sure that I am doing the "right thing".
And before you downvote this page and close it for asking too many questions, assume that I am only asking what should happen on this one specific page and why you think so.
