IPs with this type will always be solved for the current source
location. If another IP of the same type is in scope, the two locations will be
appended, creating a call-stack. The Location type is kept abstract so users
cannot create them, but a Location can be turned into a list of SrcLocs, which
correspond to individual locations in a program. Each SrcLoc contains a
package/module/file name and start/end lines and columns.
The only thing missing from the SrcLoc in my opinion is the name of the
top-level definition it inhabits. I suspect that would also be useful, but it's
not clear to me how to extract the current top-level binder from within the
constraint solver. (Surely I'm just missing something here?)
I made the (perhaps controversial) decision to have GHC completely ignore
the names of Location IPs, meaning that in the following code:
bar :: (?myloc :: Location) => String bar = foo foo :: (?loc :: Location) => String foo = show ?loc
if I call bar, the resulting call-stack will include locations for
- the use of ?loc inside foo,
- foos call-site inside bar, and
- bars call-site, wherever that may be.
This makes Location IPs very special indeed, and I'm happy to change it if the
dissonance is too great.
I've also left out any changes to base to make use of Location IPs, since there
were some concerns about a snowball effect. I think it would be reasonable to
mark this as an experimental feature for now (it is!), and defer using it in
base until we have more experience with it. It is, after all, quite easy to
define your own version of error, undefined, etc. that use Location IPs.