tibble breaking changes

• v3.1.8 \u2192 v3.2.0breaking

  Deprecated functions and arguments where we could not detect usage by other CRAN packages (#1515):

• v3.1.8 \u2192 v3.2.0breaking

  `data_frame_()`, `lst_()`, `frame_data()`

• v3.1.8 \u2192 v3.2.0breaking

  `as_tibble(validate = )`, `as_tibble(NULL)`, `new_tibble(subclass = )`

• v3.1.8 \u2192 v3.2.0breaking

  `add_row()` and `add_column()` for non-data-frame input

• v3.1.8 \u2192 v3.2.0breaking

  `add_column()` for input with non-unique names

• v3.1.6 \u2192 v3.1.7breaking

  `trunc_mat()` now returns a value with a different structure. This is considered an implementation detail that can change in the future, do not rely on it. The only guarantee is that calling `print()` will display the input like a tibble (#1059).

• v2.1.3 \u2192 v3.0.0breaking

  Subset assignment ("subassignment") and also subsetting has become stricter. Symptoms:

• v2.1.3 \u2192 v3.0.0breaking

  Error: No common type for ...

• v2.1.3 \u2192 v3.0.0breaking

  Error: Assigned data `...` must be compatible with ...

• v2.1.3 \u2192 v3.0.0breaking

  `i` must have one dimension, not 2

• v2.1.3 \u2192 v3.0.0breaking

  Error: Lossy cast from ... to ... The "invariants" article at tibble.tidyverse.org/dev/articles/invariants.html describes the invariants that the operations follow in tibble, and the most important differences to data frames. We tried to make subsetting and subassignment as safe as possible, so that errors are caught early on, while introducing as little friction as possible.

• v1.4.2 \u2192 v2.0.0breaking

  All optional arguments have moved past the ellipsis, and must be specified as named arguments. This affects mostly the `n` argument to `as_tibble.table()`, passing `n` unnamed still works (with a warning).

• v1.4.2 \u2192 v2.0.0breaking

  `new_tibble()` has been optimized for performance, the function no longer strips dimensions from 1d arrays and no longer checks correctness of names or column lengths. (It still checks if the object is named, except for zero-length input.) Use the new `validate_tibble()` if you need these checks (#471).

• v1.4.2 \u2192 v2.0.0breaking

  The `nrow` argument to `new_tibble()` is now mandatory. The `class` argument replaces the now deprecated `subclass` argument, the latter will be supported quietly for some time (#518).

• v1.4.2 \u2192 v2.0.0breaking

  Setting names on a tibble via `names(df) <- ...` now also requires minimal names, otherwise a warning is issued once per session (#466).

• v1.4.2 \u2192 v2.0.0breaking

  In `as_tibble()`, checking names is also enabled by default, even for tibbles, matrices and other matrix-like objects: names must exist, `NA` names are not allowed. Coercing a matrix without column names will trigger a warning once per session. (This corresponds to the `"minimal"` checks described below.).

Get this data programmatically \u2014 free, no authentication.