Changelog for PyF-0.8.0.1

Revision history for PyF

f (and fWithDelimiters) were renamed fmt (fmtWithDelimiters). f was causing too much shadowing in any codebase.
PyF now exposes the typeclass PyFToString and PyFClassify which can be extended to support any type as input for the formatters.
PyF now uses Data.String.IsString t as its output type if OverloadedString is enabled. It means that it behaves as a real haskell string literal.
A caveat of the previous change is that PyF does not have instances for IO anymore.

An important amount of bugfixs
Error reporting for generic formatting (i.e. formatting without a specified type) is now more robust
Template haskell splices are simpler. This leads to more efficient / small generated code and in the event of this code appears in a GHC error message, it is more readable.
PyF now longer emit unnecessary default typing.

Fixed: PyF now uses the same haskell extensions as the one used by the current haskell file to parse sub expressions.

Fixed: PyF was wrongly ignoring everything located after a non-doubled closing delimiter.
New Feature: line break can be escaped with , thus allowing string to start on a new line ignoring the initial backspace

Bump dependencies to megaparsec 7
Error message are now tested
Name in template haskell splices are stable. This increases readability of error messages
Better error message for badly formated expression

All monomorphic quasiquoters (f, fString, fText, fIO, fLazyText) are removed
Polymophic quasiquoter f' is renamed f and is the only entry point. Monomorphic users are encouraged to use the polymorphic quasiquoter with type annotation.
Formatting dependency is removed.
Previously named f quasiquoters which was exporting to Formatting.Format is removed. User of this behavior should use Formatting.now instead.

Custom delimiters, you can use whatever delimiters you want in place of { and }.