Original bug ID: 7064 Reporter:@alainfrisch Assigned to:@alainfrisch Status: closed (set by @xavierleroy on 2017-02-16T14:18:37Z) Resolution: fixed Priority: normal Severity: minor Fixed in version: 4.03.0+dev / +beta1 Category: typing Related to:#6711 Monitored by:@diml@hcarty
I think the following used to trigger a warning:
module X = ...
module Y = X
This is probably related to the introduction of module aliases.
In addition to fixing that, "deprecated" on modules should be improved in the following direction:
When the declaration for X has been marked as deprecated, accessing any of its field (X.x) should raise the warning.
It should be possible to specify the deprecated attribute for the implicit declaration resulting from a compilation unit. The most natural way is to interpreted a floating attribute [@@@ocaml.deprecated] at the top of the .mli (or .ml if there is no .mli), i.e. before any other non-attribute signature item.
This would allow to mark some stdlib modules as being deprecated (#6711).
The text was updated successfully, but these errors were encountered: