General improvements

[sda030]

General improvements

• speed performance
  • early fails
  • normalization with hash/ID lookup:
    • chapter overview (input only)
    • data frame (or string matrix?) of variables and their fixed information (labels, variable names, univariates?)
    • data frame (or string matrix?) of bivariate combinations with sigtest info (long format)
    • data frame (or numeric matrix?) of all summary_data stuff for univariates
    • data frame (or numeric matrix?) of all summary_data stuff for bivariates
    • NB: Matrices are hard to work with and do not allow grouping storage
    • vectorization, avoid looping (can be parallellized in outer loop)
    • profiling
    • avoid copying
    • vctrs, rlang, base
    • premake summarized_data and reuse it across elements, filtering as needed
    • pipe => no pipe
    • if not grouping:
      • dplyr::filter => vctrs::vec_slice()
      • dplyr::mutate => base
      • dplyr::select => base
      • dplyr::pull => base
      • bind_rows => vctrs::vec_rbind
      • remove tidyselect/data masking: all using strings for columns names internally
      • dtplyr?
• refactoring
• more memorable and logical naming of functions, arguments, etc.
• rename files so they are logical for developers
  • alphabetical order of operations
• documentation and examples
  • inheritParams
  • exemplify all non-trivial argument inputs (lists, vectors, objects)
  • better hints in error/warning messages
  • progress bars
• more robustness
  • increase test coverage
  • moduling / code refactoring
  • target package / renv
  • argument checks
• flexible arguments
• reduce size of package (in MB)
• reduce dependencies
  • find upstream packages
  • copy code when applicable
  • split functions into smaller and more robust packages
    • analyze co-dependencies
• simplify to reduce build/install time
  • Examples, tests, data, inst-folder templates/attachments

[sda030]

If you return the same type of output from multiple functions, you should create a function that consistently creates exact the same format (to avoid accidental inconsistency), and consider making it an S3 class (so you can have a custom print method)

[sda030]

@keywords internal for all internal functions having documentation