For a lists of ideas on how to contribute, please see Get involved.
- 1 Easy tasks
- 2 Walter and Andrei's Action List
- 3 Wish list for new modules
- 3.1 Containers (WIP)
- 3.2 An improved std.json (WIP)
- 3.3 Native curl replacement (WIP)
- 3.4 Better IO with ranges
- 3.5 Eventloop (WIP)
- 3.6 Compression/archiving
- 3.7 Encryption and hashing
- 3.8 An improved std.xml
- 3.9 std.database
- 3.10 Parallel algorithms
- 3.11 Native SQLite replacement
- 3.12 Native ZLib replacement
- 3.13 std.encoding
- 3.14 std.decimal
- 3.15 Existing modules which have been extended
Walter and Andrei's Action List
|Id||Description||Guides / People working on|
|1||eliminate all gratuitous use of gc|
|2||review all Phobos modules for compatibility with ranges - std.zip, for example, was done before ranges and does not work with them|
|3||use -cov to improve code coverage of Phobos modules||Browse annotated files on Codecov|
|4||make sure every function in Phobos has an example|| Reduce the |
|5||make sure every function in Phobos has Params: and Returns: sections http://www.digitalmars.com/d/archives/digitalmars/D/Phobos_Documentation_-_call_to_action_258777.html|| Reduce the |
|6||replace std.xml with something we can be proud of||https://github.com/lodo1995/experimental.xml|
|7||compile a list of popular modules in other languages and see what we should have|
|8||create a greenthreads module that works like Goroutines|
|9||create a module that enables code to be run on GPUs||dcompute|
|10||now that D can interface to C++ templates and exceptions, create the interface code to the C++ STL||Alexandru Razvan Caciulescu|
|11||review all of Phobos for @safe compatibility|| Guide to |
|12||remove dependency on autodecode from Phobos||see PR #5513 for a start|
|13||there was recently a thread on Phobos desperately needing a BigDecimal module, someone helpfully posted links to a couple of free C versions, I suggested that someone build a D wrapper for one or convert one to D. Sadly, that was the end of the discussion|
|14||I regularly ask people to write articles about D, and the situation is slowly getting better, in that more and more good ones are getting written|
|Id||Description||People working on|
|?||Complete implementation of @safe||Discussion at: https://email@example.com|
Wish list for new modules
Walter and Andrei have veto rights when it comes to inclusion of new stuff into DMD, druntime, and phobos. So if you're looking to work on new stuff either pick something from the list. Or get in contact with Walter or Andrei early during the design phase of your project. This way you can avoid a lot of frustration.
No one is working on this. It's tough to get started because, despite lots of discussion at various times on this forum, no one seems to really know what they want. Since the containers in question are well-known, it's much more a design problem than an implementation problem. There has been a lot of progress made towards GC-free containers with EMSI Containers and Eduard Staniloiu is working on a new collections framework.
An improved std.json (WIP)
Native curl replacement (WIP)
std.net.curl is a wrapper around the low-level bindings to the C library curl which has to be included in the D release. Apart from the licensing issues, it also means that maintaining and extending std.net.curl is quite hard. A replacement library is already WiP, but still needs help and tester to get ready for primetime.
Better IO with ranges
Ideally `std.stdio` should have a better range support. So far io, iopipe and Vibe.d's streaming interface emerged, but haven't got sufficient testing. `std.io` is reserved for the new io module. See also the DConf17 talk about iopipe.
Event loops have three common types.
A real time loop to play music (usually only concerned with one thread).
Per thread event loop that must take input from the OS and move events to the appropriate handler. May utilise multiple system event loops per instance, such as X11 and Wayland.
Per application event loop that takes ownership of events and messaging to threads.
Threading is also usually included with sockets for the usage by multithreaded web servers. A D (and in Phobos) implementation should take this into consideration with support of non-D event loops.
At the moment D's flagship web framework Vibe.d has an eventloop abstraction as eventcore. However, by default eventcore uses libevent - a C eventloop library. Installing this library often creates troubles as well as optimizing it. D should have a proper cross-platform event loop library with multithreading support that can be used as a general-purpose asynchronous library. Libasync is work in progress, however more testers and help is needed to make it a rock-solid library.
Opening standard compressed/archived file formats needs to just work. This includes at least zip, gzip, tar and bzip2. Of course, zip already is available and gzip is supported by the zlib module but with a crufty C API. At least gzip and bzip2, which are stream-based as opposed to file-based, should be handled via streams, which means that streams block compression/archiving. Also, since tar and zip are both file based, they should probably be handled by the same API, which might mean deprecating std.zip and rewriting it.
Encryption and hashing
This is more an implementation problem than a design problem. No one is working on it. Some work has been done here but it's unfinished. One of the ideas is to wrap OpenSSL? at first and then implement the most useful crypto primitives in D to avoid library dependency and to make them usable with CTFE.
An improved std.xml
This is a large, complicated project because we're trying to define a common API for a variety of RDBMSs. Again, it's more a design problem than an implementation problem. There is at least one current attempt at a unified interface: DDBC (See also: Database libraries or Erik Smith's DConf16 talk about A D standard database interface and implementation).
dsimcha has implemented a decent amount of these in his std.parallel_algorithm Github project, but has become somewhat frustrated and unmotivated to finish this project because so many of the relevant algorithms seem memory bandwidth bound and aren't substantially faster when parallelized than when run serially.
Native SQLite replacement
etc.c.sqlite3 is a wrapper around the low-level bindings to the C library SQLite3 which has to be included in the D release. Apart from the licensing issues, it also means that maintaining and extending this library is quite hard. There's already a SQLite Reader in alpha that takes CTFE optimizations into account, but of-course write access needs to be provided too.
Native ZLib replacement
etc.c.zlib is a wrapper around the low-level bindings to the C library Zlib which has to be included in the D release. Apart from the licensing issues, it also means that maintaining and extending this library is quite hard. The best existing library is archive.
std.encoding needs a complete overhaul. Other encoding packages as ascii, base64, utf8 could be included and a common API should unite them.
This new package could include a comprehensive set of encoder, covering (in addition to base64 and utf8) all the baseXX encoders, since they are easy addition (base16, base32, z85) and also domain specific encoders such as percent encoding (which then could be used in any replacement of the old-fashioned and incomplete std.uri module) or variable length quantity. Obviously the final list of encoders should be discussed on the NG.
Existing modules which have been extended
This list is a brief overview of developed replacements by the community. It is intended to show which modules might deserve a bit more attendance:
- std.bigint vs. extended
- std.csv vs. tsv-utils (in general a CSV module should have a Pandas-like API with full range support
- std.getopt - there are many community solutions:
- std.math vs. mir-math and ctstdmath
- std.signals vs. PhobosX.signals, observe
- std.socket vs. Vibe's sockets
- std.uri vs alphaPhobos, vibe.inet.url, arsd
- std.variant vs.taggedalgebraic