Davis Vaughan

My first instinct is to agree with @jennybc's thoughts that some of these examples shouldn't work without explicit setting of `.name_repair`. I could imagine `[

The story with `rbind()` and `cbind()` is growing so complex, I'd almost prefer to just leave them as they are, and advise people to use `vec_rbind()` and `vec_cbind()` directly instead....

Seems like you could link to `vec_rbind()` in the `tibble::add_row()` documentation. i.e. "If you would like to row bind multiple data frames together, see..." Similar for `vec_cbind()` and `tibble::add_column()`.

And `cms_patient_experience` and `household`?

Need to consider the sticky column case, like panelr. Ideally we'd be like dplyr, and just forcibly make the assumption that `[` with 1 argument `i` is going to return...

Maybe look into soft deprecating `rownames = NA` in the next major release of tibble. I think this is the only place where we allow users to keep row names...

The `format_check` build seems to be failing because I switched the include order of `cpp11/integers.hpp` and `cpp11/doubles.hpp` in `test-integers.cpp`. It seems to want to retain them in alphabetical order? I...

I have learned that because we set: https://github.com/r-lib/cpp11/blob/322e5ee67346926993cc6f464152802118250b78/.clang-format#L4 we can separate the includes into "blocks" and they will be sorted within their block. So I added a space between `cpp11/integers.hpp`...

Partly related to https://github.com/r-lib/cpp11/issues/219 But note that calling `cpp11::stop()` is not the only way this can occur. The original vroom issue was calling `cpp11::package("rlang")["warn"]` and then on the R side...

cpp11 is the one throwing the exception though?