Hi Chapel Developers -- A visitor to the office suggested a food-for-thought idea yesterday that I really liked: As a sibling to the examples/primers/ directory in the release, imagine an examples/idioms/ (or examples/patterns?) directory that would contain short snippets of code designed to answer questions like "How should I do ... in Chapel?"
(where ... might be "read an array stored on disk in column major order" or "transpose an array" or "sort an array" or "create a random vector of values" or any other idiom you can think of. I'm imagining it serving a purpose similar to stack overflow for Chapel (but with the benefit that it would be tested on a nightly basis to ensure that the answers stayed correct). The hope would be that these might be an area where the community could increasingly contribute proposed solutions over time, and the code review + commit process would serve as a means for the core Chapel team to "bless" the solution as being a good use of the language. Then, as we start moving release examples onto the web, this would serve as a form of online documentation as well. I believe we've discussed similar ideas before, but somehow this discussion of it gelled for me in a way that previous ones hadn't. No action items here, just wanted to get a wider group of people thinking about this concept, -Brad ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
