Skip to content

Remove magic in exhaustivity check #3015

Closed
@liufengyun

Description

@liufengyun

In the exhaustivity check, when decomposing a type path.B[Int, String], we get two child classes C1 and C1. The problem is how to turn the two classes into proper types related to path, Int and String?

Current implementation resorts to some ad-hoc hack which is not well-grounded. The correct way to solve the problem is to use type inference, as suggested by Martin.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions