{gt} table implementation

[shah-in-boots]

This is the final aspect needed for package release. This needs to be a clean extension of turning <mdl_tbl> objects into <gt_tbl> objects. Considering this, it may better to subclass another S3 class that extends {gt} instead of directly output a {gt} table.

• [x] Consider advantages and disadvantages of an additional S3 method implementation in a package that already has multiple S3 classes
• [ ] Determine advantages to have a subclass, such as the utility of specific functions directed towards the class (e.g. exponentiation of terms, post-hoc model adjustments, splitting/joining tables)
• [x] If we go down this round, should it be included in v0.1.0 release? ANSWER: No, let's push this to v0.2.0, with the goal of incorporating tables at that point in time.

[shah-in-boots]

The root class, the articulating object, is the beta relationship between two variables. It has to have certain characteristics to be able to calculate attributes about it and to give it "neighbors" based on context. All of this must be available or derivable from the mdl_tbl object

• context: of which model it was made in
• context: of what sequential adjustments were made to it
• type: the outcome and exposure could be continuous, categorical, or binary
• type: six combinations of types are minimally possible
• modifier: strata or data subset for the model
• modifier: interaction terms for example

Will need to formalize this thought process.