assertive: Readable Check Functions to Ensure Code Integrity

Lots of predicates (is_* functions) to check the state of your variables, and assertions (assert_* functions) to throw errors if they aren't in the right form.

Version: 0.3-3
Depends: R (≥ 3.0.0)
Imports: assertive.base (≥ 0.0-4), assertive.properties (≥ 0.0-2), assertive.types (≥ 0.0-2), assertive.numbers, assertive.strings, assertive.datetimes, assertive.files, assertive.sets (≥ 0.0-2), assertive.matrices, assertive.models, assertive.data, assertive.data.uk, assertive.data.us, assertive.reflection (≥ 0.0-2), assertive.code, knitr
Suggests: testthat
Published: 2016-03-29
Author: Richard Cotton [aut, cre]
Maintainer: Richard Cotton <richierocks at gmail.com>
BugReports: https://bitbucket.org/richierocks/assertive/issues
License: GPL (≥ 3)
URL: https://bitbucket.org/richierocks/assertive
NeedsCompilation: no
Materials: README NEWS
CRAN checks: assertive results

Downloads:

Reference manual: assertive.pdf
Vignettes: 2. Checking function inputs
3. Checklists of checks
A1. Exercise answers
1. Introduction
Package source: assertive_0.3-3.tar.gz
Windows binaries: r-devel: assertive_0.3-3.zip, r-release: assertive_0.3-3.zip, r-oldrel: assertive_0.3-3.zip
OS X Snow Leopard binaries: r-release: assertive_0.3-3.tgz, r-oldrel: assertive_0.2-4.tgz
OS X Mavericks binaries: r-release: assertive_0.3-3.tgz
Old sources: assertive archive

Reverse dependencies:

Reverse imports: gpuR, matrixpls, runittotestthat