Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

One of the questions in the "Top new questions this week" section of today's SO newsletter is Why is processing a sorted array slower than an unsorted array? which has a couple of close votes for being a duplicate. Does the criteria for putting questions in the newsletter filter out questions with close votes? Were the votes cast after the newsletter was composed?

share|improve this question
It's been viewed 870 times since yesterday, and it received 3 close votes. I think it's not going to be closed, personally, clearly most visitors with voting rights don't agree with the close votes gathered so far. – Martijn Pieters Dec 25 '12 at 20:18
And the close votes seem to be based on a sloppy reading of the title (and no reading of the post), it may be accidentally closed by others who vote to close before they read the comments or the post, but in that case, it would surely soon be reopened. – Daniel Fischer Dec 25 '12 at 20:26
@DanielFischer I guess I'm guilty, because I cast one of the close votes. But I did glance at the other question, and they seemed to be very similar. – Barmar Dec 25 '12 at 20:30
Similar in a way, but dasblinkenlight expected the search in the sorted array to be faster due to branch prediction, and wondered why it turned out to be slower. So it's a different effect (locality) due to using a boxed type that overshadows branch prediction. – Daniel Fischer Dec 25 '12 at 20:37
Ahh, now I see it. They're exactly opposite questions. I was wondering why the new question wasn't blocked by the duplicate title checker. – Barmar Dec 25 '12 at 20:43
Because the titles are not the same? – ThiefMaster Dec 25 '12 at 20:50
Like I said, "now I see it." I didn't notice the oppositeness when I cast the close vote. – Barmar Dec 25 '12 at 20:51
up vote 0 down vote accepted

It was obviously a mistake.

On a quick reading "Why is processing a sorted array slower than an unsorted array?" looks like a duplicate of "Why is processing a sorted array faster than an unsorted array?". Especially as many of us remember seeing the original question.

This has been sorted out now, and the question is reopened.

share|improve this answer
So basically you're saying that if a question is really popular, it's appopriate to put it in the newsletter even if there are close votes, because it's likely that they're erroneous. – Barmar Dec 25 '12 at 21:20
I don't think that is considered. I remember seeing the question and was going to vote to close it, but just noticed the difference. Obviously some people didn't. – Bo Persson Dec 25 '12 at 21:22
So are we talking about the algorithm for populating the newsletter or not? That was the subject of my question, we seem to have gone on a tangent about the particular example I used. – Barmar Dec 25 '12 at 21:26
I believe the newsletter goes by "popularity" alone, and doesn't consider that posts with lots of views and upvotes might have close votes as well. – Bo Persson Dec 25 '12 at 21:27

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .