Andrei Alexandrescu wrote: > I just submitted an application for GSoC 2011 on behalf of Digital > Mars. Please review and contribute to the project ideas page: > > http://prowiki.org/wiki4d/wiki.cgi?GSOC_2011_Ideas
Great. I find all of the provided projects useful. Maybe one should add ZeroMQ to the bindings project. I haven't used it myself. But it seems useful. Before I change the wiki page I'd like to receive some feedback for some ideas. Somehow I think it's important to offer not too much. Just tell what's important for you and what you really miss in D. =Improved documentation= I think there should be a standard theme (like the one you find for Java; Candydoc is a good step in that direction) and unittests should be included in the documentation (http://d.puremagic.com/issues/show_bug.cgi?id=2630). This is not much. Maybe more can be added. =Testing Framework= Building a testing framework on top of the available built-in unittests and assertions. Includes maybe also improving the built-in assert and build-in unittests (named unittests). Something like GoogleTest. =Logging Library= It was once on the list but it didn't lead to anything. Something like Google-glog. =Units Library= It was once on the list but it didn't lead to anything. Like Boost.Units. =Containers= What about better/more containers for std.container. Which? =std.sysinfo/core.cpuid= There is core.cpuid. I think it has no unittests which is bad. At least on Linux one could try parsing /proc/cpuinfo to have some tests. std.sysinfo would be an extension to core.cpuid providing system specific information that are not covered by core.cpuid. I'm going to write better descriptions in the wiki page if a project is considered interesting. Jens
