On the one hand, we use semantic versioning to signal this very kind of semantic API changes; on the other hand, base makes inflationary use of major version increments due to its large API surface, so that we end up with a sub-optimal signal/noise ratio, resulting in API consumers not
Change the parameter to only accept non-empty strings how? Using NonEmpty Char, which is a bit wonky. ''dreams of non-empty
#12494: Implementation of setenv in base incorrectly claims empty environment variable not supported on Windows -------------------------------------+------------------------------------- Reporter: ezyang | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: libraries/base | Version: 8.0.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by bergmark): paying attention anymore... :-( Do people actually care less about the base changelog than for other packages? Semantic changes are always scary since they can be missed, but your point still stands. literals'' -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12494#comment:3 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler