A complete rewrite of the apply_
functions have been performed. The initial goal was to have clearer codes to maintain, but from a user perspective, an improvement on speed should be observed as well.
On another positive note, the opportunity of the rewrite was taken to correct some bugs (see below).
mutate_matrix()
function now has access to context functions. This implements #09.The apply_
function family gained a new .force_name
argument, available for the dfl/dfw
versions. This allows better control in getting meaningful IDs to the outcomes.
.force_name
solves the issue #12Functions join_row_info()
and join_column_info()
now have more adjust
possibilities to expand matrix sizes when the join operation results in matrix expansion. This implements #10.
mutate_matrix()
can now accept statements such as mutate_matrix(ms, foo=bar)
, which was impossible before.apply_matrix_df*
now works when subgroup yields 1 x m or n x 1 matrices. This solves #13.force_name
argument.join_column_info()
made it impossible to be executed. This has now been fixed.matrixset
objects with 0 rows can now be printed.matrixset
s that yields 0-row objects is now possible.All matrixset
objects can now store matrices of class Matrix
, which allows sparse and other special matrices.
All matrixset
extractors or other manipulation functions will work as well.
This is a great way to annotate/manipulate special matrices.
.input_list
while .matrix_wise
is FALSE
. This answers #5matrixset
objects with partially or completely NULL
dimnames. This fixes #2CRAN submission.
NEWS.md
file to track changes to the package.