Tags: srghma/lean4
Tags
fix: lake: source file not in module input trace & some logs dropped (l… …eanprover#9101) This PR fixes a bug introduce by leanprover#9081 where the source file was dropped from the module input trace and some entries were dropped from the module job log. (cherry picked from commit 9db41f9)
fix: remove global `NatCast (Fin n)` instance (leanprover#8620) This PR removes the `NatCast (Fin n)` global instance (both the direct instance, and the indirect one via `Lean.Grind.Semiring`), as that instance causes causes `x < n` (for `x : Fin k`, `n : Nat`) to be elaborated as `x < ↑n` rather than `↑x < n`, which is undesirable. Note however that in Mathlib this happens anyway!
fix: remove global `NatCast (Fin n)` instance (leanprover#8620) This PR removes the `NatCast (Fin n)` global instance (both the direct instance, and the indirect one via `Lean.Grind.Semiring`), as that instance causes causes `x < n` (for `x : Fin k`, `n : Nat`) to be elaborated as `x < ↑n` rather than `↑x < n`, which is undesirable. Note however that in Mathlib this happens anyway!
chore: revise environment constant addition details (leanprover#8610) * Move constant registration with elab env from `Lean.addDecl` to `Lean.Environment.addDeclCore` for compatibility * Make module system behavior independent of `Elab.async` value
chore: revise environment constant addition details (leanprover#8610) * Move constant registration with elab env from `Lean.addDecl` to `Lean.Environment.addDeclCore` for compatibility * Make module system behavior independent of `Elab.async` value
Empty commit to re-randomize the hash. Lake uses the first characters of the Lean commit hash in its version number. When this accidentally is an all-numeric string starting with a 0, some tools expecting SemVer break. We encountered that issue on v4.21.0-rc1. This empty commit rerolls the dice on the commit hash, so we hopefully do not start with a 0 or have some non-numeric characters.
PreviousNext