base64: RFC 4648-compliant padded and unpadded base64 and base64url encodings

This is a package candidate release! Here you can preview how this package release will appear once published to the main package index (which can be accomplished via the 'maintain' link below). Please note that once a package has been published to the main package index it cannot be undone! Please consult the package uploading documentation for more information.

[maintain] [Publish]

RFC 4648-compliant padded and unpadded base64 and base64url encoding and decoding.


[Skip to Readme]

Properties

Versions 0.0.1.0, 0.1.0.0, 0.2.0.0, 0.2.0.0, 0.3.0.0, 0.3.1.0, 0.3.1.1, 0.4.0, 0.4.1, 0.4.2, 0.4.2.1, 0.4.2.2, 0.4.2.3, 0.4.2.4, 1.0
Change log CHANGELOG.md
Dependencies base (>=4.10 && <5), bytestring (>=0.10 && <0.11), deepseq (>=1.4 && <1.5), text (>=1.2 && <1.3) [details]
License BSD-3-Clause
Copyright (c) 2019 Emily Pillmore
Author Emily Pillmore
Maintainer emilypi@cohomolo.gy
Category Data
Home page https://github.com/emilypi/base64
Bug tracker https://github.com/emilypi/base64/issues
Source repo head: git clone https://github.com/emilypi/base64.git
Uploaded by topos at 2020-01-06T02:37:10Z

Modules

[Index] [Quick Jump]

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees


Readme for base64-0.2.0.0

[back to package description]

Base64

Build Status Hackage

Padded and unpadded base64 and base64url encodings for Text and ByteString values, along with their optics.

Summary

What does this library provide? Here is the summary:

There are no dependencies aside from base:

base64 dependencies

Motivation

Haskell has two main libraries for Base64: memory, and base64-bytestring.

Of these, memory is geared towards integration with other memory primitives in the library, without much of an eye towards performance, while base64-bytestring is built to exclusively address ByteString encoding and decoding, and is very performant. Many great strides have been made in the realm of Base64 performance and vectorization just in the past 5 years, which this library attempts to capture. Additionally, we attempt to fix percieved shortcomings with both APIs in the support of unpadded Base64 and Base64-url support (which memory provides, but not base64-bytestring), as well as supporting Text values (neither libraries provide).