I was doing some reviewing earlier when I came across this question, which in my view doesn't have sufficient code to constitute a reviewable question. It essentially consists of a data structure
short and a description of how values can be stored/updated in it. Edward had already left a comment, so I voted to close and was going to move on when I noticed that the question had just been answered.
I find it hard to reconcile how you can have a code review without having any code to review (it also seems to be bad form to answer questions likely to be closed), so I downvoted, commented and flagged the question as 'Not an Answer'.
The question has indeed now been closed (as broken/code not written), however the answer flag was declined as 'a moderator reviewed your flag, but found no evidence to support it'.
On the face of it, the answer reads like it is answering a question, has attracted an upvote and it was useful to the asker (see comment on question). However, that's because it was providing an alternate solution to a design question, not because it was reviewing code.
- Is the decline just one of those things / bad timing (I'm pretty sure it was handled at the same time as a bunch of spam flags), so I should just keep doing what I'm doing?
- Is 'not an answer' the wrong flag to have used here, because it doesn't provide sufficient context to the mod handling the flag. Perhaps a custom flag as suggested here, with a description of why it's not an answer would have been more appropriate?
- Am I completely off base here and I should have just left the answer alone?