[GHC] #11526: unsafeLookupStaticPtr should not live in IO

Mathieu Boespflug 0xbadcode at gmail.com
Tue Feb 2 14:38:01 UTC 2016

IMHO this dynamic linking thing is a red herring. In principle any function
call becomes potentially impure given eg the ability to shadow symbols. In
practice that's not something we do to programs. We could consider having
two tables though: an initial tackle generated at compile time that will
never change, and an aux table populated as new objects get linked in. Then
programs can "opt in" to taking into account new objects loaded dynamically
by reading (in IO) the aux table.

Sent from my mobile.

I'll have a look at the new material on the wiki shortly. It would be nice
to close out the basic distributed story.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20160202/3739231d/attachment.html>

More information about the ghc-devs mailing list