Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upstop_for_problems #465
Comments
hadley
closed this
in
7e87b45
Jul 10, 2016
This comment has been minimized.
This comment has been minimized.
|
@earino - this allows you to be super strict about parsing. I think, combined with the new spec printing behaviour, this should make it easy to rapidly prototype the correct parsing specification and, later, fail-fast if the underlying data changes. |
lock
bot
locked and limited conversation to collaborators
Sep 25, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
hadley commentedJul 10, 2016
By analogy to
httr::stop_for_status()it would be useful to have a function that threw an error if there were any parsing problems. You'd use this in automated scripts if you wanted to be really sure that the file format hadn't changed