Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Generate exhaustive pattern match for sealed types. #643

Merged
merged 2 commits into from Apr 9, 2019
Merged

Generate exhaustive pattern match for sealed types. #643

merged 2 commits into from Apr 9, 2019

Commits on Apr 9, 2019

  1. Generate exhaustive pattern match for sealed types. 

    Previously, you had to write on case at a time when pattern matching on
a sealed type. Now, you can complete on the `match` keyword and select
the "match (exhaustive)" completion item to generate all cases.  This
commit also introduces a new "match" completion (non-exhaustive) that
generates a single case and triggers a new completion at the case word,
for editors that support `CompletionItem.command`.
    @olafurpg
    olafurpg committed Apr 9, 2019
    Configuration menu
    Copy the full SHA
    1f3fbe8 View commit details
    Browse the repository at this point in the history

  2. Make match keyword tests pass on 2.11. 

    The `knownDirectSubClasses` method works less reliably in 2.11 compared
to 2.12.
    @olafurpg
    olafurpg committed Apr 9, 2019
    Configuration menu
    Copy the full SHA
    e4bf2be View commit details
    Browse the repository at this point in the history