Re: [Caml-list] ANN: angstrom

["Daniel Bünzli" <daniel.buenzli@erratique.ch>]

Le lundi, 25 juillet 2016 à 21:37, Spiros Eliopoulos a écrit :

> While such a design sometimes benefits the system _as a whole_, it certainly comes at a cost. In the case where clients are meant to explicitly handle parse errors and restart the parse _through control inversion_, the cost is the compositionality.

[…]
> For supporting composition, it's certainly better than control inversion.

The point is that clients are usually parsers themselves. You are not actually loosing compositionnality by supporting what you call "control inversion", you are increasing it by allowing the parsers to be used differently according to the context.  

A simple example is contrasting parsing gigabytes of geojson data where I might not consider an error of the underlying character stream as a catastrophic error and opt to continue the decode versus an implementation of the JOSE framework in which I really want to treat any sort of error as a catastrophic one.  

Best,

Daniel