Admin message

Due to a large amount of spam we do not allow new users to create repositories, they are "external" users. If you are a new user and want to create a repository, for example for forking GHC, open a new issue on ghc/ghc using the "get-verified" issue template

Implement namespace-specified imports and fix ExplicitNamespaces
The GHC Steering Committee has accepted [proposal 581: namespace-specified imports](https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0581-namespace-specified-imports.rst). This tightens up the specification of `ExplicitNamespaces`, allows `data` as a namespace specifier instead of `pattern`, and permits imports to use `type ..` and `data ..` to refer to all items in the corresponding namespaces. * [x] #12488 "Explicit namespaces doesn't enforce namespaces" (bug) * [x] #22581 "Explicit namespace type import can bring a value into scope" (bug) * [x] #25983 "Poor warning message with `-Wdodgy-imports` and non-existent subordinate items" (bug) * [x] #25984 "Dodgy import breaks a hiding clause" (bug) * [x] #25991 "Punned class method and associated type break explicit import" (bug) * [x] #25899 "Allow the `data` keyword in import and export lists" * [x] #25900 "Deprecate the `pattern` keyword in import and export lists" * [x] #25901 "Wildcards `..` in import and export lists"
issue