Changes between Version 13 and Version 14 of Design/DeprecationMechanisms


Ignore:
Timestamp:
Oct 6, 2015 3:02:07 PM (4 years ago)
Author:
simonmar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Design/DeprecationMechanisms

    v13 v14  
    1111Sadly, this design doesn't account for instances where a deprecated definition is explicitly imported but not actually ''used''. #2119 argues that GHC should issue a warning when an explicit import of a deprecated definition is found.
    1212
    13 '''SimonM''' If you import a `DEPRECATED` identifier, then there are two cases: either it is mentioned somewhere, in which case the deprecation warning will be shows, or it is not mentioned, in which case there will be an unused import warning (provided it is enabled), so this seems less useful than the other suggestions on this page. '''End SimonM'''
     13'''SimonM''' If you import a `DEPRECATED` identifier, then there are two cases: either it is mentioned somewhere, in which case the deprecation warning will be shown, or it is not mentioned, in which case there will be an unused import warning (provided it is enabled), so this seems less useful than the other suggestions on this page. '''End SimonM'''
    1414
    1515TODO Write formal specification.