Skip to content

Implement namespace-specified imports and fix ExplicitNamespaces

The GHC Steering Committee has accepted proposal 581: namespace-specified imports. 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.

  • #12488 (closed) "Explicit namespaces doesn't enforce namespaces" (bug)
  • #22581 (closed) "Explicit namespace type import can bring a value into scope" (bug)
  • #25983 (closed) "Poor warning message with -Wdodgy-imports and non-existent subordinate items" (bug)
  • #25984 (closed) "Dodgy import breaks a hiding clause" (bug)
  • #25991 (closed) "Punned class method and associated type break explicit import" (bug)
  • #25899 (closed) "Allow the data keyword in import and export lists"
  • #25900 (closed) "Deprecate the pattern keyword in import and export lists"
  • #25901 (closed) "Wildcards .. in import and export lists"
Edited by Vladislav Zavialov
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information