[Haskell-cafe] Instrumentation without requiring code-level changes?

[David Turner]

I doubt it'll be removed, it's occasionally useful and I don't think it
costs much to maintain.

The note does indicate that your proposed usage isn't exactly recommended,
and I agree: I would instrument everything all the time, to avoid all the
problems associated with monkey-patching and having two different sets of
performance characteristics to worry about, but it is at least possible to
do what you're trying to do with this method.

Cheers,



On 27 Jan 2017 08:30, "Saurabh Nanda" <saurabhnanda at gmail.com> wrote:

Yes, I think so, with the PackageImports extension.
>
> https://downloads.haskell.org/~ghc/7.8.2/docs/html/users_gui
> de/syntax-extns.html#package-imports
>

Thank you for this. If this works, it makes using instrumentedscotty &
instrumentedopaleye easier to use.. Btw, there's a note in the docs:

[...] Note: you probably don't need to use this feature, it was added
mainly so that we can build backwards-compatible versions of packages when
APIs change. It can lead to fragile dependencies in the common case:
modules occasionally move from one package to another, rendering any
package-qualified imports broken. [...]

I hope GHC doesn't plan to remove this extension any time soon.

-- Saurabh.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/haskell-cafe/attachments/20170127/3ab81fe7/attachment.html>