attoparsec-iso8601: Parsing of ISO 8601 dates, originally from aeson

[ bsd3, library, parsing ] [ Propose Tags ]

Parsing of ISO 8601 dates, originally from aeson.


[Skip to Readme]

Flags

Manual Flags

NameDescriptionDefault
developer

operate in developer mode

Disabled
fast

compile without optimizations

Disabled

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info

Downloads

Maintainer's Corner

For package maintainers and hackage trustees

Candidates

Versions [RSS] 1.0.0.0, 1.0.1.0, 1.0.2.0, 1.0.2.1, 1.1.0.0
Dependencies attoparsec (>=0.14.2 && <0.15), base (>=4.9 && <5), base-compat-batteries (>=0.10.0 && <0.13), text (>=1.2.3.0 && <1.3.0.0 || >=2.0 && <2.1), time (>=1.6.0.1 && <1.13), time-compat (>=1.9.4 && <1.10) [details]
License BSD-3-Clause
Copyright (c) 2011-2016 Bryan O'Sullivan (c) 2011 MailRank, Inc.
Author Bryan O'Sullivan <bos@serpentine.com>
Maintainer Adam Bergmark <adam@bergmark.nl>
Category Parsing
Home page https://github.com/haskell/aeson
Bug tracker https://github.com/haskell/aeson/issues
Source repo head: git clone git://github.com/haskell/aeson.git(attoparsec-iso8601)
Uploaded by phadej at 2022-01-01T19:05:59Z
Distributions Arch:1.0.2.1, Debian:1.0.1.0, Fedora:1.0.2.0, LTSHaskell:1.0.2.1, NixOS:1.0.2.1, Stackage:1.0.2.1, openSUSE:1.0.2.1
Downloads 38817 total (415 in the last 30 days)
Rating 2.0 (votes: 1) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2022-01-01 [all 1 reports]

Readme for attoparsec-iso8601-1.0.2.1

[back to package description]

Parsing of ISO 8601 dates.

This package is used to parse dates in aeson. It is split into a separate package to be shared by other projects that want to parse dates like aeson does.

For now, this project is located in the aeson repository and aeson itself uses the source of this package without pulling in the package as a dependency.

Stability

Since aeson depends on this package we want to be very careful about changing the format.

There may be breaking changes if we find that the format is incorrectly too lenient. We consider widening of the allowed input a non-breaking addition since all previously valid input will still parse correctly.