Why not just host it on GitHub or similar and come here to request review of parts?
I have this extension method which does much bla and even more bla if blu:
Some awesome code here.I'm specifically looking for suggestions on how much bla I need to get a real conversion going and if the bla on line 666 is not evil.
Note: This is extension method is part of the MAELitW (Most Awesome Extension Library in the World) project.
Edit: My first thought is that such an effort does not fit well into the Q&A style.
The biggest problems I see are:
- Organisation, tagging and stuff. I'm not very fond of creating tags just for that purpose. Also, one question per method? Per Type? Per Collection?
- Review, to avoid duplication and fragmentation questions need to be edited, which will render most answers useless, or at best confusing. Deleting questions or answers for cleanup will destroy valuable information. Marking questions as old will need a link to the newest question, which turns into much work after some time.
- Forks, if there's such a thing for .NET, there'll also be such projects for Java, C++ and similar, including all kinds of libraries.
- Megalomania, why stop at extension methods? We can host a whole Driver-Suite here!
Edit2:
one question per extension method
That means you'll need a special tag for it, which does not collide with the normal usage of the site.
duplication shouldn't be a problem, close as duplicate; when would an answer be edited so that answers (improved functions) become obsolete?; questions shouldn't be deleted, but closed;
If you close as duplicate to a newer version, you'll get a Duplicate-Chain in time, with different versions cluttering up the site. Answers might become outdated only if you edit the original question.
forks and megalomania: true, which is why I first posted it as a SE site proposal. There is a limit to how far you can take this within SE. An extension method library is the simplest form of loosely coupled methods I can think of, which makes it a nice proof of concept.
Not really, no. Where's the difference between a library with extension methods and a library with some static methods? Additionally, extension methods can use each other (as far as I know), which means that they can interact with each other and can gain the same complexity as any other library. If you have code, it doesn't matter how loosely coupled it is as long as you wrap it under one umbrella, it's still one big piece.