The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

Design Principles for linelist

This vignette outlines the design decisions that have been taken during the development of the linelist R package, and provides some of the reasoning, and possible pros and cons of each decision.

This document is primarily intended to be read by those interested in understanding the code within the package and for potential package contributors.

Scope

linelist provides a lightweight layer to add tags to data.frame columns. This allows:

Input/Output/Interoperability

Because of its scope, linelist is intended to provide maximum compatibility with data.frames, or packages defining subclasses of data.frames.

We prefer not adding a new feature, rather than having this feature alter the usual behaviour of a data.frame.

One notable exception to this rule are data.table since they differ too much from the standard data.frame behaviour, which makes it difficult to ensure compatibility.

make_linelist() is the main user-facing function of this package. It takes a data.frame/tibble/X as input as returns an output of class c("linelist", "data.frame")/c("linelist", "tibble")/c("linelist", "X"). As a consequence, differences in behaviour between data.frame and tibble are still present after conversation to a linelist object.

Design decisions

Dependencies

Because of its strong interoperability with the tidyverse packages, it is accepted for linelist to depend on low-level tidyverse or r-lib packages, such as rlang, vctrs or tidyselect.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.