Skip to content

Slighly suboptimal error messages when inheriting from non-existent type #1548

@0x53A

Description

@0x53A

This was tested using latest master.

Repro steps

Compile Project A:

module B
type PublicType() =
    member x.Y() = ()
type private PrivateType() =
    member x.Y() = ()

Try to compile Project B:

type E() =
    inherit B.Type()
    member x.Y() = ()

Actual behavior

Provide a description of the actual behaviour observed.
image

  1. The error message is printed thrice.
  2. Instead of a linebreak, some symbol is printed (maybe related to the new conhost in W10?)
  3. The new heuristic offers all types, even ones that are not visible (PrivateType) (cc @forki)

Related information

  • Operating system Windows 10
  • Branch master

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

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions