Displaying 2 results from an estimated 2 matches for "sisaltable".
2016 Feb 11
2
inconsistency in treatment of USE.NAMES argument
...230
/rgbif/R/zzz.r:120
/rjstat/R/rjstat.R:75
/rlist/R/internal.R:155
/rnoaa/R/homr.R:140
/rnoaa/R/storm_shp.R:42
/roxygen2/R/template.R:27
/rplos/R/fulltext.R:29
/rplos/R/fulltext.R:82
/shiny/inst/tests/test-bootstrap.r:12
/shinyjs/inst/examples/demo/helpers.R:49
/simcausal/R/network.R:319
/sisal/R/sisalTable.R:806
/sisal/R/sisalTable.R:829
/sisal/R/sisalTable.R:853
/sisal/R/sisalTable.R:915
/sisal/R/sisalTable.R:924
/sisal/R/sisalTable.R:933
/stringdist/R/seqdist.R:130
/stringdist/R/stringdist.R:286
/surveillance/R/calibration_null.R:25
/surveillance/R/calibration_null.R:185
/surveillance/R/epidata.R:3...
2016 Feb 08
2
inconsistency in treatment of USE.NAMES argument
Hi,
Both vapply() and sapply() support the 'USE.NAMES' argument. According
to the man page:
USE.NAMES: logical; if ?TRUE? and if ?X? is character, use ?X? as
?names? for the result unless it had names already.
But if 'X' has names already and 'USE.NAMES' is FALSE, it's not clear
what will happen to the names. Are they going to propagate to the
result