[Haskell-cafe] Instrumentation without requiring code-level changes?
saurabhnanda at gmail.com
Fri Jan 27 09:00:03 UTC 2017
The PackageImports hack doesn't seem to be working. Is this a peculiarity
of the extension, or of GHCi, or have I gotten the imports/exports wrong --
Note: The package-qualified import and my package name are the **same**
On Fri, Jan 27, 2017 at 2:08 PM, David Turner <dct25-561bs at mythic-beasts.com
> 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.
> On 27 Jan 2017 08:30, "Saurabh Nanda" <saurabhnanda at gmail.com> wrote:
> Yes, I think so, with the PackageImports extension.
> 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...
More information about the Haskell-Cafe