I think my short term solution is going to be remove -auto-all from attoparsec's cabal---I'm not profiling attoparsec and so I don't want my entire profile output to be internal attoparsec functions. But presumably the flag was added there for a reason, so maybe there are people who really want that.
Yes - me :-)
Yes, certainly it makes sense for someone profiling the library itself, or if I thought your library was too slow and wanted to send a profile in a bug report. But I don't think it makes so much sense for plain users, especially when it's applied only to some libraries. However, this seems to be a fairly common practice... at least parsec3 and text both do this, which is why I initially thought parsec3 was so much slower than parsec2, and attoparsec-text was doubly slow.
I might, though, see if there's a way I could enable that flag only for myself (in a way that I wouldn't routinely forget).
This sounds like a good idea to me.