Skip to content

[enhancement] do not report deprecation usage messages in functions which are deprecated themselves #2230

Open
@jurgenvinju

Description

@jurgenvinju

Is your feature request related to a problem? Please describe.

The standard library currently produces 21 warnings like this:

[WARNING] /util/Reflective.rsc:160:015: Deprecated function: Function will be moved to Rascal compiler

All of these are uses of functions which are deprecated by functions which are deprecated themselves.

  • since we will be removing these functions entirely, the warning about what happens in their bodies is not useful
  • the implicit message that we have risky code that users should be warned about in the standard library isn't true.
  • the warning can not be solved by re-implementing the bodies of these functions better, and also it would be a waste.

So perhaps it would be good to filter or not produce these warnings in this specific circumstance of being a deprecated function that uses deprecated functions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions