Comments (4)
That is intended, the behavior of 1.5 being a backward incompatible change. Yes, the fix was not quick...
from math-comp.
Just to be sure, the 1.5 -> 1.6 fix is the change you're speaking of ? I.e. that we have two incompatible changes in the picture: the one from 1.4 to 1.5 (when apply started to add goals for evars) and the one from 1.5 to 1.6 when this behaviour has been reverted ?
As a side note, is there a 1.5 -> 1.6 ChangeLog somewhere ?
from math-comp.
There is such a ChangeLog, shipped with the distribution here:
https://github.com/math-comp/math-comp/blob/master/etc/ChangeLog.
But it only mentions the issues with the library.
The corresponding (and so far more detailed) log for the tactic language is at the end of the manual:
https://github.com/math-comp/ssr-manual/blob/master/changes.tex
But it looks like we've not pushed content for versions >= 1.5 ...
Thanks for spotting that!
from math-comp.
There is no real changelog for the plugin because nothing really new happened.
Only two fixes, one for apply (that breaks wrt 1.5 and restores 1.4 behavior) and one for elim (that should accept more lemmas I believe).
from math-comp.
Related Issues (20)
- Investigate slowness of mathcomp's vs. coq's GitLab CI builds
- vm_compute getting very slow HOT 14
- Please pick the version you prefer for Coq 8.18 in Coq Platform 2023.10 HOT 13
- Naive parametric instance problem HOT 5
- Performance problem with multiple rewrite in mathcomp2 HOT 1
- does `leq_subr` follow the naming convention?
- rpred expose the iinternal of Num.real HOT 5
- Disable warning about redundant projection
- Semi-modules and semi-algebras HOT 3
- Incoherence of the implicit status of lemmas HOT 6
- Refactor qpoly and poly HOT 2
- Detailed installation instructions with make HOT 2
- `fun_scope` and `function_scope` HOT 5
- `Bind Scope` declarations for structure record types
- Remove 1.16.0 deprecations HOT 1
- Check MC1 backports HOT 2
- Avoid exporting warning settings
- Require Import order issue with associativity settings HOT 1
- Building with COQ 8.19 results in `Error: A left-recursive notation must have an explicit level.` in `fingroup/presentation.v` HOT 4
- Mono in partial order morphisms HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from math-comp.