aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
* Adding test for bug #3417.Gravatar Pierre-Marie Pédrot2014-11-30
|
* Test for bug #3485.Gravatar Pierre-Marie Pédrot2014-11-30
|
* Fixing printing of dirpathes in Ppconstr. It was reversed.Gravatar Pierre-Marie Pédrot2014-11-30
|
* Test for bug #3487.Gravatar Pierre-Marie Pédrot2014-11-30
|
* Test of bug #3682.Gravatar Pierre-Marie Pédrot2014-11-30
|
* Fixing bug #3682.Gravatar Pierre-Marie Pédrot2014-11-30
| | | | | The function initializing proofviews were marking all evars as non-resolvables for the proofview, while only goal evars ought to be.
* Adding missing unsafe primitives to Proofview.Gravatar Pierre-Marie Pédrot2014-11-30
|
* fix compilation on ocaml 3.12 (Close: 3833)Gravatar Enrico Tassi2014-11-28
|
* Fix (somewhat obsolete) [Existential] command, which conflicted with the shelf.Gravatar Arnaud Spiwack2014-11-28
| | | | | When an evar was instantiated it failed to disapear from the shelf. It had the consequence of stopping Qed from happening. Fixes test-suite/success/apply.v
* Tactic primitives: missing [advance] lead to spurious dangling goals.Gravatar Arnaud Spiwack2014-11-28
| | | Closes #3801.
* STM: if a-p-always-delegate fetch states from parked worker on edit-atGravatar Enrico Tassi2014-11-28
| | | | | | | | If the async-proofs-always-delegate is passed, workers are killed only when the proof they computed is obsolete. If one jumps back to a state that was computed by the worker (and not the master) instead of (re)computing such state in the master ask the worker to send it back.
* Future: API for blocking futuresGravatar Enrico Tassi2014-11-28
|
* Reverting the following block of three commits:Gravatar Hugo Herbelin2014-11-27
| | | | | | | | | | | - Registering strict implicit arguments systematically (35fc7d728168) - Experimenting always forcing convertibility on strict implicit arguments (a1a6d7b99eef5e6) - Fixing Coq compilation (894a3d16471) Systematically computing strict implicit arguments can lead to big computations, so I suspend this attempt, waiting for improved computation of implicit arguments, or alternative heuristics going toward having more conversion in rewrite.
* FAQ: fix some broken urlsGravatar Pierre Letouzey2014-11-27
|
* STM: hook called whenever a state is unreachableGravatar Enrico Tassi2014-11-27
| | | | Even indirectly, if it depends on another state that in turn failed.
* typosGravatar Enrico Tassi2014-11-27
|
* Fix test flags for fake_ideGravatar Enrico Tassi2014-11-27
|
* better to always print the thread idGravatar Enrico Tassi2014-11-27
|
* async_queries_* merged with async_proofs_*Gravatar Enrico Tassi2014-11-27
|
* AsyncTaskQueue: parsin can also happen in the workers nowGravatar Enrico Tassi2014-11-27
|
* STM: new API async_queryGravatar Enrico Tassi2014-11-27
| | | | | | | | When async_proofs_always_delegate is on, park proof workers and dispatch to them queries. This flips the current way of printing goals in PIDE base UIs: it is not the worker that prints all goals while coomputing the states (and the dies), it is the UI that asks for them when they are under the eyes of the user.
* AsyncTaskQueue: API to park a workerGravatar Enrico Tassi2014-11-27
| | | | | | | | | | | | Generalize the old model by letting one park a worker and by letting the (parked) worker be picky about the tasks it picks up. The use of that is the following: a proof worker, while performing its "main" task (building a proof term) computes all the intermediate states but returns only its main result. One can ask the worker to hang around, and react to special tasks, like printing the goals of an intermediate state.
* WorkerPool: API to move a worker from an active pool to a parking oneGravatar Enrico Tassi2014-11-27
| | | | | | | This lets me have a pool of active workers of a fixed size, plus a parking area where workers that completed their job can stay holding their state (and eventually one can ask them to query such state afterwards).
* TQueue: let reader be picky when popping an itemGravatar Enrico Tassi2014-11-27
| | | | E.g. let a worker pick up only jobs he is able to deal with.
* STM: put hooks in key events to let plugins customize the feedbackGravatar Enrico Tassi2014-11-27
| | | | The default hook value is the one used by CoqIDE
* Feedback: API cleaned up, documented and made user extensibleGravatar Enrico Tassi2014-11-27
|
* Fixing Coq compilation.Gravatar Pierre-Marie Pédrot2014-11-26
|
* Experimenting always forcing convertibility on strict implicit argumentsGravatar Hugo Herbelin2014-11-26
| | | | in tactic unification.
* Registering strict implicit arguments systematically.Gravatar Hugo Herbelin2014-11-26
|
* Bug #3804 is actually closed (thanks to Jason Gross for the notification).Gravatar Xavier Clerc2014-11-25
|
* Tweak some test cases.Gravatar Xavier Clerc2014-11-25
|
* Fix order of arguments in Extract Constant for Pos.compare_cont.Gravatar Maxime Dénès2014-11-25
|
* Adding tag output to references in Ppconstr.Gravatar Pierre-Marie Pédrot2014-11-25
|
* Used an evar name based on the local def name in "evar" tactic.Gravatar Hugo Herbelin2014-11-25
|
* A bit more information in debug tactic unification.Gravatar Hugo Herbelin2014-11-25
|
* Adapting to current semantics of "simpl non-evaluable-cst"Gravatar Hugo Herbelin2014-11-25
|
* Experimenting using unification when matching evar/meta free subtermsGravatar Hugo Herbelin2014-11-25
| | | | | | | | | | | | | | while before these were supposed to consider only syntactically. Made the experiment to unify with all delta flags unset. Keeping the same flags as for non evar/meta free subterms would lead to too much successes, as e.g. "true && b" matching "b" when the modulo_conv_on_closed_terms flag is set, which is the case for rewrite. But maybe should we instead investigate to have the same flags but with the restrict_conv_on_strict_subterms flag set. This rules out examples like "true && b" unifying with "b" and this is another option which is ok for compiling the stdlib without any changes.
* Plugging console highlighting in for toplevel and compilation error messages.Gravatar Pierre-Marie Pédrot2014-11-24
|
* Adding test for bug #3248.Gravatar Pierre-Marie Pédrot2014-11-24
|
* Fixing bug #3817.Gravatar Pierre-Marie Pédrot2014-11-24
| | | | | | | | Coqtop was wrongly assuming that receiving a SIGINT when reading on a channel meant that the channel was closed, resulting in a crash when interrupting an idle coqtop from CoqIDE. To prevent this, we block SIGINTs when reading in ide_slave.
* Pass around information on the use of template polymorphism forGravatar Matthieu Sozeau2014-11-23
| | | | | | | inductive types (i.e., ones declared with an explicit anonymous Type at the conclusion of their arity). With this change one can force inductives to live in higher universes even in the non-fully universe polymorphic case (e.g. bug #3821).
* One more word about "simpl f": avoid "simpl f" to be printed "simpl f",Gravatar Hugo Herbelin2014-11-23
| | | | at least when f is an evaluable reference.
* Add printer for transparent state for ocamldebug.Gravatar Hugo Herbelin2014-11-23
|
* Partly revert commit d9681fb94a3e04a618e58cd09df9cee929170edc aboutGravatar Hugo Herbelin2014-11-23
| | | | | when the arguments of a constructor can be moved at the place of the variable on which destruct or induction applies.
* Fix #3824. de Bruijn error in normalization of fixpoints.Gravatar Maxime Dénès2014-11-23
| | | | | | This bug was affecting the VM and the native compiler, but only in the pretyper (not the kernel). Types of arguments of fixpoints were incorrectly normalized due to a missing lift.
* Specific printer of Evar.Set.t for ocamldebug + more information inGravatar Hugo Herbelin2014-11-22
| | | | a UserError to ease debugging.
* Attempt to organize and document unification flags of setoid rewrite.Gravatar Hugo Herbelin2014-11-22
|
* Removing superfluous newlines in setoid_rewrite error message.Gravatar Hugo Herbelin2014-11-22
|
* In setoid_rewrite error messages:Gravatar Hugo Herbelin2014-11-22
| | | | | | - removed the encapsulation in a Tactic Failure (I don't see why setoid_rewrite should specifically raise a Fail - do I miss something?) - avoid having twice a "Unable to satisfy ... constraints" message.
* Test for closed #2713 and #2876.Gravatar Hugo Herbelin2014-11-22
|