GitLab

Note that PRIdPTR is considered as linux-ism so it's not available on platforms
like Solaris, although some other free Unix(-like) OSes apparently supports
it too.

Based on a patch from markwright in #3072.

Consider
   Work item:   k ~ *
   Inert item:  (a::k) ~ Int

Then we must kick out the inert item!  We weren't doing that,
something I discovered when fixing Trac #7384.

Discussed with Dimitrios, and we wrote a long comment
Note [Delicate equality kick-out] to explain.

I think I accidentally introduced this bug a month ago when
refactoring. It's a bit non-obvious, but since Derived constraints
have no evidence, we mustn't be strict in it.  Now there's a big
comment to prevent this bug happening again.

This fixes Trac #7384.

This bug caused Trac #7386, because in the (rather tricky) "type
inference" (aka run time type reconstruction) done by the GHCi
debugger, we were failing to instantiate a data type family
correctly.  When that code was written we didn't *have* data
families.

I wrote Note [Constructor arg types] to explain the new scheme.

There's no need to have the uniq in the rule, but its presence can
cause spurious ABI changes.

There are no longer any GLOBAL_VARs in main/DriverMkDepend.hs.

We now do the initial dependency generation for the vanilla way
regardless of what way flags and hisuf/osuf flags are given. This
makes it easier to generate the right dependency info in the end.

These names end up in the ABI, and hence part of the ABI hash.
We don't want uniques in them so that we don't get spurious ABI
hash changes.

The wrapper functions can end up in interface files, and thus are
part of the ABI hash. But uniqs easily change for no good reason
when recompiling, which can lead to an ABI hash needlessly changing.

We don't want to narrow the argument size before making the foreign
call: Word8 still gets passed as a Word-sized argument

This was causing crashes in stm050(ghci), throwto001(ghci), and
possibly more.

By shear luck I think this didn't lead to any actual runtime crashes,
but it did cause some problems for debugging.