Hadley Wickham

That looks more like a white-space delimited file than what you normally see in a FWF. And `read_table()` does work: ``` r readr::read_table(I(c(" col1 col2 col3", "first middle last"))) #>...

Because it's very rare for fwf columns to have reasonable column names, since column widths are typically very small.

I assume that this has been fixed.

I can reproduce this too: ``` r library(readr) parse_guess("49555598868235", guess_integer = FALSE) #> [1] 4.95556e+13 parse_guess("49555598868235", guess_integer = TRUE) #> [1] 266206987 parse_integer("49555598868235") #> [1] 266206987 ``` Created on 2023-07-31...

If it's simple to implement and doesn't affect much downstream code, it seems like it's worth adhering to the `as.data.frame` API contract (such as it is).

If it's going to cause revdep failures, that clearly pushes it in to the "not worth it" category, IMO.

OTOOH this would be nice for dbplyr, where we could avoid a query if we new the column names

That seems like a reasonable approach to me, but I don't know enough about the behaviour of `install.packages` to say for sure (there's probably no foolproof way to capture every...

I suspect these are mostly going to be css/js clashes and hence (currently) outside the scope of hugodown, but it's worth documenting them listing known work arounds.

It would be good to figure out why the checks aren't being run. Do you see any other errors?