This adds a helper function `fwf_cols` that is a more intuitive way of specifying fixed width column start and end points. While `fwf_positions` requires three vectors for start, end, and names, `fwf_cols` accepts a named list of length-2 vectors of the column start and end positions.

It needs the .Rd file.

This adds a helper function `fwf_cols` that is a more intuitive way of specifying fixed width column start and end points. While `fwf_positions` requires three vectors for start, end, and names, `fwf_cols` accepts a named list of length-2 vectors of the column start and end positions.

It needs the .Rd file.

This adds a helper function `fwf_cols` that is a more intuitive way of specifying fixed width column start and end points. While `fwf_positions` requires three vectors for start, end, and names, `fwf_cols` accepts a named list of length-2 vectors of the column start and end positions.

- read_fwf arg col_positions will check for column names and whether the data frame is widths or a start/end data frame.
- rewrite fwf_cols to accept named args of length 1 or 2. This makes it more concise. Also accept a data frame as the first argument
- More checks for argument validity
- Use tibbles instead of lists where appropriate

Some tests failing. Still need to debug.

Move fwf_col_names function lower in file.

See tidyverse#616

Add widths form of fwf_cols to documentation

See tidyverse#616

This is too complicated; since we have fwf_cols, don't worry about list inputs.

See tidyverse#616

Revert added newline

See tidyverse#616

Remove a try() call since, the preference is for errors to bubble up to users.

See tidyverse#616

This seems too flexible, so I'll change it to just use ...

See tidyverse#616

See comments in tidyverse#616

- removed tests that failed after removing features in fwf_cols in previous commits
- remove test that failed because fwf_positions changes columns to numeric

Revert this section in read_fwf since it is unnecessary to handle data list objects with the availability of fwf_cols

See tidyverse#616

Convert some numeric constants to integer constants so that addition/subtraction does not coerce columns to numeric if they were integer. This is not a big deal, but since the positions represent integers anyways, it might as well keep them as such if they are already specified as such.

weird things happened to NEWS.md. They are fixed now.