The OpenD Programming Language

OpenD Libraries

See the library reference index for details.

Some packages allow you to import them with the top level name. Note this will not import the entire hierarchy; it is just a curated list of common modules under it.

A design goal of OpenD is for things to just work. To help achieve this, it bundles several libraries from various sources in the initial download, meaning you can `import` them and use them without any further effort!

However, since they come from multiple sources, there's some differences between them that might matter to you.

First-party Supported OpenD Bundled Library Namespaces
Package License Status Remarks
d.* MR Experimental Status planned to stabilize with OpenD language
arsd.* Varied Active Extended stdlib
core.* MR Active Parts subject to change with language releases
std.*, etc.* MR Legacy Provided for compatibility with existing upstream D code
deimos.*, bindbc.* Varied Legacy C library bindings

See also the dpldocs search engine.

Glossary

Status Terms

Active
The library is actively maintained and developed. Breakage is possible as part of enhancement efforts, but efforts are made to control it.
Legacy
Legacy libraries prioritize compatibility with old code over other concerns. They are less likely to receive new features than actively developed libraries, but also less likely to require your attention to fix breakage on updates.
Experimental
The library is new and unfinished. It might have major changes, breakages, or face abandonment in the future.
Minimal
The library is minimally maintained and not likely to receive significant fixes or enhancements. Unlike Legacy libraries, it is possible it will break in the future due to neglect.
Untested
The library has not been tested and may work beautifully or might not even compile!

License Terms

MR (Minimally Restrictive)
The library is under license terms that put few or no restrictions on your code that uses the library. This means licenses like Boost, public domain, etc.
Varied
The library is predominantly under minimally restrictions licenses, but has portions under other licenses, so you should check the documentation of the specific parts you use.
Other
The library uses other license. Might be MIT, BSD, GPL, proprietary, anything that doesn't fit the definition above of "minimally restrictive".

Remember that compliance with all licenses in your programs is your responsibility.