-
Notifications
You must be signed in to change notification settings - Fork 0
Does it terminate? #1
Comments
Did anyone have time to look at this issue? I am about to remove the opam package of |
I remember this package to be known as taking a very long time to terminate: on Jenkins @MatejKosik had created a bench with it and a bench without. @herbelin or any of the experienced developers know about this package and should be able to comment further. |
OK thanks. |
For information, I added this package to a black list for https://coq-bench.github.io/ |
@clarus this project is maintained upstream, so this repo could be considered obsolete: https://github.com/vrahli/NuprlInCoq I think we can keep the packages for historical preservation purposes. |
See also coq-community/manifesto#60 (comment). I proposed to archive the coq-contrib copy of the repository, but didn't get any answer. |
I have a question. It seems to me that this package takes a really long time to compile. I tested the
v8.6.0
release and:Is it just me or this package is extremely slow? Does it terminate? The next question being: at which point being slow is considered as a bug and should we continue to distribute an opam package for it?
The text was updated successfully, but these errors were encountered: