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

Remove --no-coverage-check option #1918

Closed
asr opened this issue Mar 27, 2016 · 7 comments
Closed

Remove --no-coverage-check option #1918

asr opened this issue Mar 27, 2016 · 7 comments
Assignees
Labels
type: enhancement Issues and pull requests about possible improvements
Milestone

Comments

@asr
Copy link
Member

asr commented Mar 27, 2016

{-# OPTIONS --no-coverage-check #-}

data  : Set where
  zero :succ :id : ℕ
id (succ n) = succ n

z : ℕ
z = id zero

-- When normalising `z` (C-c C-n), I got
--
-- An internal error has occurred. Please report this as a bug.
-- Location of the error: src/full/Agda/TypeChecking/CompiledClause/Match.hs:191

-- Tested with 2.4.2.5 and master.
@asr asr added the type: bug Issues and pull requests about actual bugs label Mar 27, 2016
@UlfNorell
Copy link
Member

Is there a good reason to keep --no-coverage-check, or can we just remove it?

@asr
Copy link
Member Author

asr commented Mar 27, 2016

If you remove --no-coverage-check you get an error due to the missing pattern matching id zero in the definition of id.

Edit (2016-03-28). After reread Ulf's comment and my answer, I don't know what I was thinking...

@UlfNorell
Copy link
Member

Which is what you would expect. What I mean is, are there legitimate cases where --no-coverage-check makes sense? It's quite easy to emulate it with a catch-all and a postulate.

@asr
Copy link
Member Author

asr commented Mar 27, 2016

What I mean is, are there legitimate cases where --no-coverage-check makes sense?

Good question! I don't know any legitimate example.

@andreasabel
Copy link
Member

Before Nisse @nad insisted to make this an internal error, there was an error like "Incomplete matching for function id" triggered by "id zero". However, from our perspective in only arose for Agda bugs, as no one used --no-coverage-check.
I think --no-coverage-check could go to the attic, but it might be worthwhile asking on the Agda list first.

@asr
Copy link
Member Author

asr commented Apr 6, 2016

I think --no-coverage-check could go to the attic, but it might be worthwhile asking on the Agda list first.

No one requested the option, so I'll remove it.

@asr asr changed the title __IMPOSSIBLE__ triggered when using the --no-coverage-check option Remove --no-coverage-check option Apr 6, 2016
@asr asr added type: enhancement Issues and pull requests about possible improvements and removed type: bug Issues and pull requests about actual bugs labels Apr 6, 2016
@asr asr added this to the 2.5.1 milestone Apr 6, 2016
@asr asr self-assigned this Apr 6, 2016
@asr asr closed this as completed in d14b90b Apr 7, 2016
@asr
Copy link
Member Author

asr commented Apr 13, 2016

Relevant for #1845.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement Issues and pull requests about possible improvements
Projects
None yet
Development

No branches or pull requests

3 participants