Shelby Bearrows

Your data would actually be read correctly with `readr::read_table()` which handles whitespace delimited files with any number of whitespace characters between columns. Unfortunately, we are not currently pursuing replicating this...

I was working on https://github.com/tidyverse/readr/issues/1388 and wanted to see what it would do in vroom. Given the above, I was surprised that the following works without error: ``` r t...

@jennybc I believe this is ready for another look!

@melissagwolf For now, the `id` column needs to be named in `col_select` to be included in the output, like this: ``` r out1 #> 1 file16c7378aa3650.csv 1 2 #> 2...

@jennybc It seems like this is due to vroom since I can replicate the parsing error with edition 1 ``` r library(readr) with_edition( 1, read_csv(readr_example("challenge.csv"), show_col_types = FALSE) ) #>...

The most common usage of `problems()` that I can see are either a user specifies `col_types` but there is some data later on that is unexpected and doesn't match `col_types`...

@jennybc this is ready for your edits!

Note to self: Right now `spec_csv()` is going through edition 1 `read_csv()` which ends up in `col_spec_standardise` and that has it's own custom name repair machinery https://github.com/tidyverse/readr/blob/85cf1e8e664e2a75eba393f91d89b39060140dab/R/col_types.R#L441-L458 The fact that...

> Is there a reason not to do something along these lines? Same as @DavisVaughan, it would solve the problem especially in the long term for removing readr edition 1...

I know that `spec_csv()` is basically already a wrapper for ed1 `spec(read_csv(n_max = 0, guess_max = guess_max))` so I guess it's not the "wrapper" bit that feels odd. Maybe I'm...