Simon Michael

Thanks for this report @the-solipsist. https://hledger.org/1.50/hledger.html#combining-costs-and-equity-conversion-postings and the following section try to set appropriate expectations for this feature, but I think that doc could be improved to cover your example,...

And I agree that it would be nice if this feature could be made more robust, handling more kinds of entries.

Related to @Xitian9's #2292.

I can no longer reproduce the crash, and processes now sort correctly by nice value. (I don't know if there's any secondary sort for all the processes with nice=0, I'm...

Woo that's a lot! Let's keep it simple, max_byte_used looks the most useful. This is quite a specific feature, but useful to haskell devs like us. How about calling it...

If used with a non-haskell program, or a haskell program not compiled the right way, what happens ? Is it worth using GHC's RTS stats, or could we get the...

Currently, quickbench is positioned as a really quick and easy (quick and dirty, some might say) reporting tool - "a better `time`". I think adding a lot of specialist measurements...

I'm not against adding a simple "memory" measurement for haskell programs, as I'd personally find that very handy, but I wonder how far to go.

I'd also love to show "transactions per second" in these reports when benchmarking hledger or other PTA apps. Supporting such custom metrics, somehow, would be another nice feature (and scope...

Increasingly off topic, but while we're brainstorming: I wished for an easy display of changes (perhaps only between two executables). Eg to summarise results for two hledger versions I made...