Skip to content

Printing of type signatures has inaccuracies, especially from --sig:file.fsi #393

@drvink

Description

@drvink

Printing of type signatures has inaccuracies, especially from --sig:file.fsi

  1. See case OptionalAttribute and DefaultParameterValueAttribute is not output to signature file by --sig option #2684

  2. See case When "module rec" is used, a file that can not be compiled is output by --sig option #2685

  3. See case Some exotic constraints are missing corresponding signature constructs #675

  4. The type signatures printed by the compiler in error messages seem to be the most accurate (though not always entirely), but the ones printed by FSI and the signature file generator facility are particularly bad. As an example, try generating a signature file from the code in issue Compiler sometimes suggests constraints that are impossible to write #392--it's almost entirely wrong (the signature file embedded in that issue was written mostly by hand, just to clarify).

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugImpact-Low(Internal MS Team use only) Describes an issue with limited impact on existing code.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions