Johan Tibell
Johan Tibell
This is documented for the main package (ekg) http://hackage.haskell.org/package/ekg but perhaps at least ekg-core, which provides the GC metrics, needs some docs as well.
I believe the common practice is to use a space but use parenthesis (or sometimes newlines, for big records) for clarity e.g. `f (x {...})`. In general I try to...
Having raw metrics is very useful when the client library (in my case in Haskell) is doing some aggregation itself and need to communicate the pre-aggregated metric through statsd to...
Can confirm that it still exists. In my case I have package.json and my handlers in the same directory.
Would a global `DecodeOptions` option do (i.e. never quote any fields) or do you need per-field control?
Sounds like a good idea. I will get around to it eventually.
Thanks for the tip. I will take a look when I find some spare time.
That sounds like a good idea. I'm currently on a 2.5 month vacation so I won't have the time to look into it until I'm back I'm afraid.
The parameter should go in `EncodeOptions`, would you like to give it a try? You would have to edit `Data.Csv.Encoding.escape` to take the `EncodeOptions` record as a parameter and then...
I read the Python docs and it's not clear from the description above if you want exactly what Python has, namely both a `doublequote` and an `escapechar` setting.