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.

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

Term name resolution change #5296

Merged

Conversation

mitchellwrosen
Copy link
Member

Overview

Implementation notes

Interesting/controversial decisions

Test coverage

Loose ends

runarorama and others added 30 commits August 10, 2024 22:29
The quotes seem to be preventing the UI from loading on my system
and quotes are not needed in this situation in Batch.
I ran into this when i tried running it in a non-POSIX shell. Nothing
happened. Bash, when asked to run a script without a shebang will
interpret it itself, while other shells behave differently (and I think
this even depends on the OS – BSD (like macOS) & Linux handle `execvp`
differently).

This adds a shebang and some “strict” settings.
From #5179, there’s a case where we hit an `error "impossible"`, which
doesn’t provide much context. This turns it into a parse failure, so we
have #thte state of the lexer when this happens again. It also adds a
comment that describes when this “impossible” case gets hit.
Previously, `match` and `cases` expressions needed to have at least one
pattern to match on. This allows them to work with zero patterns, which
is useful for matching on empty types.

Since `EmptyMatch` is no longer a failure case, errors that previously
said “I expected some patterns after a match / with or cases but I
didn't find any,” now say “Pattern match doesn't cover all possible
cases”.

Fixes #4731.
Support pattern matching on empty types
Turn a possible “impossible” into a parse failure
@mitchellwrosen mitchellwrosen merged commit 7d7df0e into type-name-resolution-change Aug 26, 2024
2 of 5 checks passed
@mitchellwrosen mitchellwrosen deleted the term-name-resolution-change branch August 26, 2024 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants