Recently I've seen an increase in people voting for LCC when I don't agree this is the correct reason. These all seem to be getting LCC VTC because they're lacking description.
- Looping through this list takes time
- Displaying a paginated list of forum topics using PHP PDO
- Loop on dataframe takes a lot of time
- Find sum of neighbors in a 2D array
- Sign-up serialization in Python
Existing Close Reason
Lacks concrete context: Code Review requires concrete code from a project, with sufficient context for reviewers to understand how that code is used. Pseudocode, stub code, hypothetical code, obfuscated code, and generic best practices are outside the scope of this site.
Lacks Concrete Context is purely about code, not descriptions.
- "unclear what you're asking" vs "Lacks concrete context"
- When we changed the close reasons description wasn't an existing close reason, nor was it included into the close reason.
- The problem with insufficient context
- Need clarification on my close reason interpretation for a specific close reason
Since this has been going on for over a year now, with no sign of improving. Should we accept that the reason is confusing, and should be changed.
Maybe a rewording to say:
- It's limited to just code;
- To use UCWYA for description; or
- To remove all instances of the word 'context.'
I'd hope one of these would help, but I'm no linguist.
Should we clarify the close reason?
- Yes: What should we clarify it to?
- No: How can we fix this scenario?