Let me preface this by saying that nobody should ever be punished for trying to be a positive contributor to the community.

I, for one, do not have any experience in this tag. However, the question seems to tick all the boxes for a question to be an topic—

1. Has a meaningful title
2. Introduces/describes the problem well
3. Describes the warning along with the code that produces it
4. Has associated code sample

From first glance, your question should not have been closed, even if the answer did not address it properly.

What should've been done was a constructive comment left, possibly a downvote (I'd expect it based on the user(s) you were dealing with), and possibly a better answer, as Hans noted.

What instead happened was that someone took it upon themselves to punish you for the answer you wrote, by posting a close vote request on the SO Close Vote Reviewers chatroom. The specific close reason given was

too broad ("someone make my code compliant" - self-answered, not useful for future readers)

Thankfully, sanity has prevailed, and a moderator reopened your question. If this happens again, I'd recommend flagging your question for moderator attention and explaining the situation.

Note: This post has been revised based on the discussion in the comments under this answer. Most of the inflammatory comments/remarks from the previous version of this answer have been removed.

Let me preface this by saying that nobody should ever be punished for trying to be a positive contributor to the community.

I, for one, do not have any experience in this tag. However, the question seems to tick all the boxes for a question to be an topic—

1. Has a meaningful title
2. Introduces/describes the problem well
3. Describes the warning along with the code that produces it
4. Has associated code sample

From first glance, your question should not have been closed, even if the answer did not address it properly.

What should've been done was a constructive comment left, possibly a downvote (I'd expect it based on the user(s) you were dealing with), and possibly a better answer, as Hans noted. This did happen sans answer, however I do not approve of the manner in which it was done.

Additionally, your question was posted on the SO Close Vote Reviewers for auditing, and upon further inspection, was closed by other users with experience in the C tag (link redacted, see edit history for link). 

The specific close vote reason cited there was—

too broad ("someone make my code compliant" - self-answered, not useful for future readers)

Upon further review, a moderator reopened your question, which I'm glad has been done. I did not agree with the closure of your question, but apparently I'm in the minority. I'll let the majority vote win out here.