Timeline for Closing questions of the same pattern or answering them for the use case?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 21, 2017 at 22:41 | history | edited | Hannah VernonMod | CC BY-SA 3.0 |
deleted 1 character in body
|
| Jul 28, 2017 at 18:25 | comment | added | Hannah Vernon Mod | Close as Duplicate is indeed a bit problematic since every question is always going to have some difference. Closing as duplicate offers a quick way for us to help the OP without having to re-write the answer with slight modifications every time. | |
| Jul 28, 2017 at 18:10 | comment | added | Evan Carroll | I don't think I have anything special to add in the generic, nor would I argue that it's a wrinkle. It's just I was going to show up a test, sample code, and a benchmark for his use case. I think that would provide extra value to him. That's likely true of all question we close for following a pattern. | |
| Jul 28, 2017 at 18:06 | history | answered | Hannah VernonMod | CC BY-SA 3.0 |