Consolidate CodePage in System.Win32.NLS with the CodePage in base-4.15

[RyanGlScott]

Both Win32 and base-4.15 define identical (but distinct) type synonyms named CodePage. I propose that Win32 re-export the CodePage from base when possible.

Current Behavior

As of base-4.15, the GHC.IO.Encoding.CodePage module defines a type synonym named CodePage:

type CodePage = DWORD

As it turns out, the Win32 library also defines an identical (but distinct) type synonym named CodePage in System.Win32.NLS:

win32/System/Win32/NLS.hsc

Line 72 in b297380

type CodePage = UINT

(Note that DWORD = UINT = Word32.) This creates problems for code that tries to use both System.Win32.NLS and GHC.IO.Encoding.CodePage together, as their two CodePage definitions will clash.

Steps to Reproduce (for bugs)

An example of a library that this actually affected in practice in code-page, which stopped building after base-4.15's release. See RyanGlScott/code-page#5. It's possible to work around the issue, but if Win32 simply re-exported CodePage from base, this bug would have never happened in the first place.

Your Environment

• Version used: GHC 9.0.1 (base-4.15.0.0 and Win32-2.10.0.0)
• Operating System and version: 64-bit Windows 10

[RyanGlScott]

#170 implements this idea.

[Mistuke]

Thanks for the issue and PR @RyanGlScott, do you need a release before the scheduled monthly one?

[RyanGlScott]

Thanks! And I'm not in a hurry to get this released to Hackage, so the current release schedule is fine.