As agreed by the community, editing a question to include changes suggested in answers is a bad edit, and these edits are regularly rolled back, for a good reason: we want the answers to refer to the code in the question, as the OP's code was when it was reviewed. There's no questioning that.
But that's generally true for iterative reviews.
The first answer posted on this question made a number of assumptions about OP's code, which caused the following comment (emphasis mine):
Mat. My dude. I really wish you would have just dropped a comment real quick to clarify instead of making so many (incorrect) assumptions. As a result, all but the last few paragraphs are irrelevant to me. The answer has some nice factoids that might be useful to some readers but now if I edit my post, I will invalidate your answer. I am partially to blame for using var so sorry. In all actuality the Paginate extension returns a PagedList! You can figure it out from there. The last few paragraphs are helpful to me though so thanks. I will have a think about which approach to take. – Caster Troy 1 hour ago
Indeed, I should have commented and asked for clarifications instead of making [wrong] assumptions.
We've agreed to edit our respective posts; both the question and my answer were properly edited.
Is there anything wrong with this kind of approach towards edits if it's initiated by the answerer?
Oh.. how about I scratch the first two strikes off that answer then? – Mat's Mug 48 mins ago
