We intend to provide regular “minor version” releases of the Lean language at approximately monthly intervals. There is not yet a strong guarantee of backwards compatibility between versions, only an expectation that breaking changes will be documented in this file.
This file contains work-in-progress notes for the upcoming release, as well as previous stable releases. Please check the releases page for the current status of each version.
Development in progress.
Release candidate, release notes will be copied from the branch releases/v4.15.0 once completed.
Full Changelog: https://github.com/leanprover/lean4/compare/v4.13.0...v4.14.0
structure and inductive commands
inductive or structure. Recall that a Prop-valued inductive type is a syntactic subsingleton if it has at most one constructor and all the arguments to the constructor are in Prop. Such types have large elimination, so they could be defined in Type or Prop without any trouble. The way inference has changed is that if a type is a syntactic subsingleton with exactly one constructor, and the constructor has at least one parameter/field, then the inductive/structure command will prefer creating a Prop instead of a Type. The upshot is that the : Prop in structure S : Prop is often no longer needed. (With @arthur-adjedj).structure command can now define recursive inductive types:structure Tree where n : Nat children : Fin n → Tree def Tree.size : Tree → Nat | {n, children} => Id.run do let mut s := 0 for h : i in [0 : n] do s := s + (children ⟨i, h.2⟩).size pure s
Type* elaborator could lead to incorrect universe parameters with the inductive command.:= variants of inductive and structure (see breaking changes).Application elaboration improvements
@[elab_as_elim] require at least one discriminant, since otherwise there is no advantage to this alternative elaborator.@x.f elaborates as @S.f with x supplied to the appropriate parameter.CoeFun instances. For example, Mathlib has Multiset.card : Multiset α →+ Nat, and now with m : Multiset α, the notation m.card resolves to ⇑Multiset.card m... ellipses in patterns made use of optparams and autoparams.set_option structure.strictResolutionOrder true makes inconsistent parent orderings into warnings.Recursion and induction principles
let bindings.Predefinition.Structural.Error messages
match expressions (@josojo).calc error messages.#5627 and #5663 improve the #eval command and introduce some new features.
ToExpr instance, which means hoverable output. If ToExpr fails, it then tries looking for a Repr or ToString instance like before. Setting set_option eval.pp false disables making use of ToExpr instances.Repr instances, enabled with the pp.derive.repr option (default to true). For example:inductive Baz | a | b #eval Baz.a -- Baz.aIt simply does
deriving instance Repr for Baz when there's no way to represent Baz.eval.type controls whether or not to include the type in the output. For now the default is false.#eval do return 2, where monad is unknown, work. It tries unifying the monad with CommandElabM, TermElabM, or IO.Lean.Eval and Lean.MetaEval have been removed. These each used to be responsible for adapting monads and printing results. Now the MonadEval class is responsible for adapting monads for evaluation (it is similar to MonadLift, but instances are allowed to use default data when initializing state), and representing results is handled through a separate process.MonadEval class applies, then the error message will be specific about missing ToExpr/Repr/ToString instances.MetaM and CoreM wouldn't collect log messages.let rec could not be used in #eval.partial definitions
New tactic configuration syntax. The configuration syntax for all core tactics has been given an upgrade. Rather than simp (config := { contextual := true, maxSteps := 22}), one can now write simp +contextual (maxSteps := 22). Tactic authors can migrate by switching from (config)? to optConfig in tactic syntaxes and potentially deleting mkOptionalNode in elaborators. #5883, #5898, #5928, and #5932. (Tactic authors, see breaking changes.)
simp tactic
Fin literals to reduce more consistently.simpa ... using t where metavariables in t were not properly accounted for, and also improves the type mismatch error.simp! to actually talk about simp!.attribute [simp ←] (note the reverse direction). This adds the reverse of a theorem as a global simp theorem.decide tactic
decide! tactic for using kernel reduction (warning: this is renamed to decide +kernel in a future release).bv_decide tactic
bv_toNat tag for toNat_ofInt (@bollu).at in ac_nf and uses it in bv_normalize (@tobiasgrosser).getLsbD bitblaster theory.bv_check to warning.~~~(-x) support.ac_nf by default.bv_decide counter example.BitVec.sdiv support.BitVec.ofBool support.if support.bv_normalize.conv mode
congr conv tactic to handle “over-applied” functions.arg conv tactic so that it can access more arguments and so that it can handle “over-applied” functions (it generates a specialized congruence lemma for the specific argument in question). Makes arg 1 and arg 2 apply to pi types in more situations. Adds negative indexing, for example arg -2 is equivalent to the lhs tactic. Makes the enter [...] tactic show intermediate states like rw.Other tactics
generalize ... at * would apply to implementation details (@ymherklotz).classical tactic combinator.apply and simp elaborate, making them not disable error recovery. This improves hovers and completions when the term has elaboration errors.deriving clauses
#5065 upstreams and updates #where, a command that reports the current scope information.
Linters
Metaprogramming interface
pushGoal/pushGoals and popGoal for manipulating the goal state. These are an alternative to replaceMainGoal and getMainGoal, and with them you don't need to worry about making sure nothing clears assigned metavariables from the goal list between assigning the main goal and using replaceMainGoal. Modifies closeMainGoalUsing, which is like a TacticM version of liftMetaTactic. Now the callback is run in a context where the main goal is removed from the goal list, and the callback is free to modify the goal list. Furthermore, the checkUnassigned argument has been replaced with checkNewUnassigned, which checks whether the value assigned to the goal has any new metavariables, relative to the start of execution of the callback. Modifies withCollectingNewGoalsFrom to take the parentTag argument explicitly rather than indirectly via getMainTag. Modifies elabTermWithHoles to optionally take parentTag?.getFunInfo and inferType to use withAtLeastTransparency rather than withTransparency.RecursorVal.getInduct to return the name of major argument’s type. This makes “structure eta” work for nested inductives.mkRecursorInfoForKernelRec.Lean.Expr.name? recognizer for Name expressions.liftCommandElabM to preserve more state, fixing an issue where using it would drop messages.m! strings, for example m!"{.ofConstName n}".structure parents in the StructureInfo environment extension.Other fixes or improvements
runtime.maxHeartbeats (@eric-wieser).ac_nf0 and simp_arith so that the kernel is less prone to reducing expensive atoms.#version command that prints Lean's version information.Expr.proj).rwa tactic.WorkspaceClientCapabilities to make applyEdit optional, in accordance with the LSP specification (@pzread).initialize and builtin_initialize participate in the call hierarchy and other requests.#5640 fixes a bug where goal states in messages might print newlines as spaces.
#5643 adds option pp.mvars.delayed (default false), which when false causes delayed assignment metavariables to pretty print with what they are assigned to. Now fun x : Nat => ?a pretty prints as fun x : Nat => ?a rather than fun x ↦ ?m.7 x.
#5711 adds options pp.mvars.anonymous and pp.mvars.levels, which when false respectively cause expression metavariables and level metavariables to pretty print as ?_.
#5710 adjusts the ⋯ elaboration warning to mention pp.maxSteps.
#5759 fixes the app unexpander for sorryAx.
#5827 improves accuracy of binder names in the signature pretty printer (like in output of #check). Also fixes the issue where consecutive hygienic names pretty print without a space separating them, so we now have (x✝ y✝ : Nat) rather than (x✝y✝ : Nat).
#5830 makes sure all the core delaborators respond to pp.explicit when appropriate.
#5639 makes sure name literals use escaping when pretty printing.
#5854 adds delaborators for <|>, <*>, >>, <*, and *>.
Array
Array.data.Array.swapAt!.Array.mapIdx lemmas to a new file.Array.mapIdx.Array.reduceOption.Array.isEqv and BEq.Array.shrink to Array.take, and relates it to List.take.List.modify, adds lemmas, relates to Array.modify.Array.forIn and List.forIn.Array.forIn', and relates to List.Init.Data.Array.Basic to not recommend the deprecated constant.LawfulBEq (Array α) ↔ LawfulBEq α.@[simp] from back_eq_back? to back_push.Array.back to back!.List
List.redLength.List.mapIdx and adds lemmas.List.foldxM_map.List.join to List.flatten.List.sum.prefix_append_right_inj as a simp lemma.List.drop_drop addition order.List.bind and Array.concatMap to flatMap.List.pure to List.singleton.ne_of_mem_of_not_mem.ne_of_apply_ne.List.modify lemmas.List.groupBy to splitBy.for loops over List with foldlM.Nat
Fixed width integers
BitVec
BitVec.[getMsbD|getLsbD|msb] for shifts (@luisacicolini).BitVec.udiv/umod/sdiv/smod after add/sub/mul/lt (@tobiasgrosser).udiv normal form to be /, resp. umod and % (@bollu).toFin (@tobiasgrosser).BitVec.(getMSbD, msb)_(add, sub) and BitVec.getLsbD_sub (@luisacicolini).BitVec.[udiv|umod]_[zero|one|self] (@tobiasgrosser).BitVec.sdiv_[zero|one|self] (@tobiasgrosser).BitVec.(msb, getMsbD, getLsbD)_(neg, abs) (@luisacicolini).BitVec.toInt_sub, simplifies BitVec.toInt_neg (@tobiasgrosser).intMin the smallest signed bitvector (@alexkeizer).(msb, getMsbD)_twoPow (@luisacicolini).BitVec.[zero_ushiftRight|zero_sshiftRight|zero_mul] and cleans up BVDecide (@tobiasgrosser).BitVec.(msb, getMsbD)_concat (@luisacicolini).Hashable (BitVec n)String/Char
HashMap
HashMap.modify/alterOther
@[simp] from Option.isSome_eq_isSome.Prod.Antisymm to Std.Antisymm.Sum.Nat.log2_two_pow (@spinylobster).ForIn instances.@[simp] from Sum.forall and Sum.exists.Decidable assumptions (@FR-vdash-bot).-f flag and adds the -g flag (@James-Oswald).--short-version (-V) option to display short version (@juhp).lake new math to use autoImplicit false (@eric-wieser).Lake not create core aliases in the Lake namespace.text option for buildFile* utilities.lake init not git init when inside git work tree (@haoxins).lean-toolchain file on lake update if it finds the package’s direct dependencies use a newer compatible toolchain. To skip this step, use the --keep-toolchain CLI option. (See breaking changes.)lake build <pkg>:release.OfScientific is called with raw literals (@eric-wieser).applyDerivingHandlers now takes one fewer argument, registerDerivingHandlerWithArgs is now simply registerDerivingHandler, DerivingHandler no longer includes the unused parameter, and DerivingHandlerNoArgs has been deprecated. To migrate code, delete the unused none argument and use registerDerivingHandler and DerivingHandler. (#5265)--lean CLI option for lake was removed. Use the LEAN environment variable instead. (#5684)inductive ... :=, structure ... :=, and class ... := syntaxes have been deprecated in favor of the ... where variants. The old syntax produces a warning, controlled by the linter.deprecated option. (#5542)TacticM to make use of the current recovery state. Commands that wish to elaborate configurations should now use declare_command_config_elab instead of declare_config_elab to get an elaborator landing in CommandElabM. Syntaxes should migrate to optConfig instead of (config)?, but the elaborators are reverse compatible. (#5883)Full Changelog: https://github.com/leanprover/lean4/compare/v4.12.0...v4.13.0
structure command
rfl and apply_rfl tactics
unfold tactic
unfold do zeta-delta reduction of local definitions, incorporating functionality of the Mathlib unfold_let tactic.omega tactic
simp tactic
simp apply rules with higher-order patterns.induction tactic
induction’s “pre-tactic” block to always be indented, avoiding unintended uses of it.ac_nf tactic
ac_nf, a counterpart to ac_rfl, for normalizing expressions with respect to associativity and commutativity. Tests it with BitVec expressions.bv_decide
extractLsb' the primitive bv_decide understands, rather than extractLsb (@alexkeizer)bv_decide diagnoses.bv_decide normalization rules for ofBool (a.getLsbD i) and ofBool a[i] (@alexkeizer)bv_decidebv_decide counterexample at the APIBitVec.ofNat with Nat fvars in bv_decidebv_normalize rules.bv_normalize pipeline to support more general preprocessing passesbv_normalize up-to-date with the current BitVec rewritesElaboration improvements
elab_as_elim procedure.elab_as_elim to allow arbitrary motive applications._ arguments now.let bindings and fun binders if possible. Makes “cannot synthesize metavariable” errors take precedence over unsolved universe level errors.ite in the discriminant of match-expression when reducibility setting is .reducibleDeriving handlers
Repr deriving instance handle explicit type parametersFunctional induction
Linters
Other fixes
.. appears with a . on the next lineMetaprogramming
Meta.evalExpr (@eric-wieser)Inhabited (TacticM α) (@alexkeizer)inferType.MVarId.assertHypotheses to set BinderInfo and LocalDeclKind.MVarId.tryClearMany', a variant of MVarId.tryClearMany.#5222 reduces allocations in Json.compress.
#5231 upstreams Zero and NeZero
#5292 refactors Lean.Elab.Deriving.FromToJson (@arthur-adjedj)
#5415 implements Repr Empty (@TomasPuverle)
#5421 implements To/FromJSON Empty (@TomasPuverle)
Logic
dite_not/decide_not with only Decidable (¬p).ite_eq_left_iffInhabited (Sum α β) instancesLawfulBEqNonempty instances for products, allowing more partial functions to elaborate successfullyheq_comm@[simp] from exists_prop' to exists_propBool
BitVec
BitVec.getElem_zeroExtend@[simp] from some BitVec lemmasBitVec.intMin/Max from abbrev to defBitVec.getElem_truncate (@tobiasgrosser)bv_decide (@bollu)BitVec unsigned order theoretic resultstoNat_sub_of_le (@bollu)BitVec.truncate lemmasBitVec.setWidth to unify zeroExtend and truncate (@tobiasgrosser)BitVec.ofBool_[and|or|xor]_ofBool theorems (@tobiasgrosser)BitVec.getElem_* (@tobiasgrosser)Nat.{mul_two, two_mul, mul_succ, succ_mul} (@bollu)BitVec.toNat_{add,sub,mul_of_lt} for BitVector non-overflow reasoning (@bollu)_self, _zero, and _allOnes for BitVec.[and|or|xor] (@tobiasgrosser)BitVec.[and|or|xor] (@tobiasgrosser)BitVec.toInt_[intMin|neg|neg_of_ne_intMin] (@tobiasgrosser)BitVec.[not_not, allOnes_shiftLeft_or_shiftLeft, allOnes_shiftLeft_and_shiftLeft] (@luisacicolini)BitVec.(shiftLeft_add_distrib, shiftLeft_ushiftRight) (@luisacicolini)sdiv_eq, smod_eq to allow sdiv/smod bitblasting (@bollu)BitVec.toNat_[abs|sdiv|smod] (@tobiasgrosser)BitVec.(not_sshiftRight, not_sshiftRight_not, getMsb_not, msb_not) (@luisacicolini)BitVec.Lemmas - drop non-terminal simps (@tobiasgrosser)BitVec.divRec_succ'BitVec.getElem_[add|add_add_bool|mul|rotateLeft|rotateRight… (@tobiasgrosser)Bitvec.[add, sub, mul]_eq_xor and width_one_cases (@luisacicolini)List
List.mergeSort lemmasmergeSort comparator autoParamList.length_mergeSortmap_mergeSortmergeSortList.Basic without List.ImplList.head_mem and similarList.attachList.tail_mapList.attach lemmasList.count lemmasList.filterList.mem_ite_nil_left and analoguesList.findIdx / List.take lemmasList.getElem_takeList.findIdx theoremsList.all/any lemmasList.countP lemmasList.tail lemmaList.getElem_memList.replicate lemmasList.attachWith lemmasList.head_mem_head?List.tailList.erase / List.find lemmasList.fold / attach lemmasList.fold relatorsList.maximum?List.toArrayList.set_mapList.IsPrefix (@Command-Master)List.set_replicate_selfList.maximum? to max?List.fold lemmas@[simp] on List.getElem_mem etc.List.unattach and simp lemmasList.min?_consArray
Array.data to Array.toListList.getElem_append variantsArray.not_mem_emptyArray functions either semireducible or use structural recursionDecidableEq (Array α)@[simp] on Array.swapAt!_defArray.foldX lemmasList.toArraytoArray_concatArray.eraseRepsArray.qsortOrdSubarray.emptyArray.length_toListArray.modify lemmasArray.flatten lemmas[]! indexing to rely on hypothesis (@TomasPuverle)Array.size_feraseIdxArray/Option.unattachOption
Nat
Int
Fin
HashMap
DHashMap|HashMap|HashSet).(getKey?|getKey|getKey!|getKeyD)Lean.(HashSet|HashMap)HashSet.ofArrayHashSet.partitionSingleton/Insert/Union instances for HashMap/SetHashSet.all/anyInsert/Singleton/Union instances for HashMap/Set.RawHashSet.Raw.all/anyMonads
Simp lemma cleanup
run_new_frontend signaturenoncomputablesrc/lake/lakefile.toml to the adjusted Lake build processlean.h compile with MSVC (@kant2002)Reservoir build cache. Lake will now attempt to fetch a pre-built copy of the package from Reservoir before building it. This is only enabled for packages in the leanprover or leanprover-community organizations on versions indexed by Reservoir. Users can force Lake to build packages from the source by passing --no-cache on the CLI or by setting the LAKE_NO_CACHE environment variable to true. #5486, #5572, #5583, #5600, #5641, #5642.
#5504 lake new and lake init now produce TOML configurations by default.
#5878 fixes a serious issue where Lake would delete path dependencies when attempting to cleanup a dependency required with an incorrect name.
Breaking changes
@[builtin_doc] attribute (@digama0)groupBy.loop (@vihdzp)BitVec.mul docstring (@llllvvuu)Lean.MetavarContextLean.withSeconds (@alexkeizer)toUIntX functions (@TomasPuverle)inferType does not ensure type correctnessrelease-ci label via comment (@thorimur)lean-pr-testing-NNNN branches should use Batteries’ lean-pr-testing-NNNN brancheslake-manifest.json when updating lean-pr-testing branchespr-release.ymlbv_decide tactic. This release introduces a new tactic for proving goals involving BitVec and Bool. It reduces the goal to a SAT instance that is refuted by an external solver, and the resulting LRAT proof is checked in Lean. This is used to synthesize a proof of the goal by reflection. As this process uses verified algorithms, proofs generated by this tactic use Lean.ofReduceBool, so this tactic includes the Lean compiler as part of the trusted code base. The external solver CaDiCaL is included with Lean and does not need to be installed separately to make use of bv_decide.
For example, we can use bv_decide to verify that a bit twiddling formula leaves at most one bit set:
def popcount (x : BitVec 64) : BitVec 64 := let rec go (x pop : BitVec 64) : Nat → BitVec 64 | 0 => pop | n + 1 => go (x >>> 2) (pop + (x &&& 1)) n go x 0 64 example (x : BitVec 64) : popcount ((x &&& (x - 1)) ^^^ x) ≤ 1 := by simp only [popcount, popcount.go] bv_decide
When the external solver fails to refute the SAT instance generated by bv_decide, it can report a counterexample:
/-- error: The prover found a counterexample, consider the following assignment: x = 0xffffffffffffffff#64 -/ #guard_msgs in example (x : BitVec 64) : x < x + 1 := by bv_decide
See Lean.Elab.Tactic.BVDecide for a more detailed overview, and look in tests/lean/run/bv_* for examples.
simp tactic
reducePow simproc.index option to the dsimp tactic, introduced to simp in #4202.Fin.isValue simproc.simpCtorEq simproc to reduceCtorEq and makes it optional. (See breaking changes.)reduceCtorEq is enabled in the norm_cast tactic.reduce steps for trace.Debug.Meta.Tactic.simp trace messages.ext tactic
induction tactic
let bindings in minor premises wouldn't be counted correctly.omega tactic
conv tactic
arg n to handle subsingleton instance arguments.#5044 upstreams the #time command.
#5079 makes #check and #reduce typecheck the elaborated terms.
Incrementality
where clauses in declarations.case .. | .. tactic.Definitions
clean_wf tactic to clean up tactic state in decreasing_by. This can be disabled with set_option debug.rawDecreasingByGoal false.backward.eqns.deepRecursiveSplit option can be set to false to get the old behavior. See breaking changes.f.eq_unfold lemmas. Now Lean produces the following zoo of rewrite rules:Option.map.eq_1 : Option.map f none = none Option.map.eq_2 : Option.map f (some x) = some (f x) Option.map.eq_def : Option.map f p = match o with | none => none | (some x) => some (f x) Option.map.eq_unfold : Option.map = fun f p => match o with | none => none | (some x) => some (f x)The
f.eq_unfold variant is especially useful to rewrite with rw under binders.Variable inclusion
include currently only applies to theorems.Elaboration
(· + ·)) would not handle ambiguous notation correctly. Numbers the parameters, making this example expand as fun x1 x2 => x1 + x2 rather than fun x x_1 => x + x_1.inductive commands could create terms that the kernel rejects.variable could fail when mixing binder updates and declarations.Other fixes or improvements
syntheticHole parser so that hovering over _ in ?_ gives the docstring for synthetic holes.rename_i where implementation detail hypotheses could be renamed.Lsp.Diagnostics.@[app_delab], a macro for creating delaborators for particular constants. The @[app_delab ident] syntax resolves ident to its constant name name and then expands to @[delab app.name].#print output for structures.pp.exprSizes debugging option. When true, each pretty printed expression is prefixed with [size a/b/c], where a is the size without sharing, b is the actual size, and c is the size with the maximum possible sharing.#5020 swaps the parameters to Membership.mem. A purpose of this change is to make set-like CoeSort coercions to refer to the eta-expanded function fun x => Membership.mem s x, which can reduce in many computations. Another is that having the s argument first leads to better discrimination tree keys. (See breaking changes.)
Array
List
List.findIdx lemmas.List.Sublist lemmas, some upstreamed. #5077 fixes implicitness in refl/rfl lemma binders. add List.Sublist theorems.List.Pairwise lemmas.List.find?/findSome?/findIdx? theorems.List.foldlRecOn and List.foldrRecOn recursion principles to prove things about List.foldl and List.foldr.List.Perm.List.mergeSort and a fast @[csimp] implementation.List.subset more aggressive.List.getLast?_cons.List.range and List.iota lemmas.List.join lemmas.List.append lemmas.List.erase(|P|Idx) lemmas.List.attach and List.pmap.List.find? and List.range'/range/iota lemmas.List.Pairwise_erase and related lemmas.List simp lemmas. #5105 and #5102 adjust List simp lemmas.List.getLast_eq_iff_getLast_eq_some as a simp lemma.List.getElem_drop and List.getElem_drop'.@[csimp] lemmas earlier where possible.Nat and Int
Nat.add_left_eq_self and relatives.Nat.and_xor_distrib_(left|right).Nat and Int simp lemma confluence.Int simp lemmas.Int lemmas relating neg and emod/mod.Int.toNat_sub simp lemma.Nat.bitwise lemmas.Option
BitVec
sshiftRight bitblasting.Std.Associative and Std.Commutative instances for BitVec.[and|or|xor].missingDocs error for BitVec modules.BitVec more consistent.BitVec.intMin. Introduces boolToPropSimps simp set for converting from boolean to propositional expressions.BitVec.getLsb to BitVec.getLsbD, etc., to bring naming in line with List/Array/etc.UInt
UInt lemmas.Std.HashMap and Std.HashSet
Std.Sat (for bv_decide)
Parsec
Thunk
Thunk.ext.IO
Other fixes or improvements
Array, Bool and Prod utilities from LeanSAT.Relation.TransGen.trans.WellFoundedRelation Nat using <, not Nat.lt.≠ instead of Not (Eq ...) in Fin.ne_of_val_ne.Fin.le_antisymm.refine'.if-then-else and Option.ULift and PLift.omega theory.Bool simp lemmas.Function.comp simp lemmas.if-then-else simp lemmas.@[elab_as_elim] to Quot.rec, Nat.strongInductionOn and Nat.casesStrongInductionOn, and also renames the latter two to Nat.strongRecOn and Nat.casesStrongRecOn (deprecated in #5179).allowUnsafeReducibility.simp tactics.Expr equality test.Expr equality test.PreDefinition transformations if they are not needed.CheckAssignmentQuick in ExprDefEq.instantiateMVarDeclMVars, used by runTactic.Expr.betaRev.stderrAsMessages is now the default on the command line as well.instantiateMVars. Normally delayed assignment metavariables are never directly assigned, but on errors Lean assigns sorry to unassigned metavariables.addMatcherInfo.Frontend.processCommand and FrontendM are no longer used by Lean core, but they will be preserved.AUTO_THREAD_FINALIZATION feature on Windows.LEAN_EXPORTs for Windows.readBinFile and readFile now only require two system calls (stat + read) instead of one read per 1024 byte chunk.Handle.getLine and Handle.putStr no longer get tripped up by NUL characters.libleanshared on Windows to avoid symbol limit, removes the LEAN_EXPORT denylist workaround, adds missing LEAN_EXPORTs.actions/cache in CI.save-always in cache actions in CI.git syntax in pr-release workflow.pr-release workflow pass --retry to curl.libleanshared_1 on macOS.leanmanifest in each build.restart-on-label workflow also filter by commit SHA.LibUV is now required to build Lean. This change only affects developers who compile Lean themselves instead of obtaining toolchains via elan. We have updated the official build instructions with information on how to obtain LibUV on our supported platforms. (#4963)
Recursive definitions with a decreasing_by clause that begins with simp_wf may break. Try removing simp_wf or replacing it with simp. (#5016)
The behavior of rw [f] where f is a non-recursive function defined by pattern matching changed.
For example, preciously, rw [Option.map] would rewrite Option.map f o to match o with … . Now this rewrite fails because it will use the equational lemmas, and these require constructors – just like for List.map.
Remedies:
o before rewriting.rw [Option.map.eq_def], which rewrites any (saturated) application of Option.map.set_option backward.eqns.nonrecursive false when defining the function in question. (#4154)The unified handling of equation lemmas for recursive and non-recursive functions can break existing code, as there now can be extra equational lemmas:
Explicit uses of f.eq_2 might have to be adjusted if the numbering changed.
Uses of rw [f] or simp [f] may no longer apply if they previously matched (and introduced a match statement), when the equational lemmas got more fine-grained.
In this case either case analysis on the parameters before rewriting helps, or setting the option backward.eqns.deepRecursiveSplit false while defining the function.
The reduceCtorEq simproc is now optional, and it might need to be included in lists of simp lemmas, like simp only [reduceCtorEq]. This simproc is responsible for reducing equalities of constructors. (#5167)
Nat.strongInductionOn is now Nat.strongRecOn and Nat.caseStrongInductionOn to Nat.caseStrongRecOn. (#5147)
The parameters to Membership.mem have been swapped, which affects all Membership instances. (#5020)
The meanings of List.getElem_drop and List.getElem_drop' have been reversed and the first is now a simp lemma. (#5210)
The Parsec library has moved from Lean.Data.Parsec to Std.Internal.Parsec. The Parsec type is now more general with a parameter for an iterable. Users parsing strings can migrate to Parser in the Std.Internal.Parsec.String namespace, which also includes string-focused parsing combinators. (#4774)
The Lean module has switched from Lean.HashMap and Lean.HashSet to Std.HashMap and Std.HashSet (#4943). Lean.HashMap and Lean.HashSet are now deprecated (#4954) and will be removed in a future release. Users of Lean APIs that interact with hash maps, for example Lean.Environment.const2ModIdx, might encounter minor breakage due to the following changes from Lean.HashMap to Std.HashMap:
get instead of find, (#4943)map[key] no longer returns an optional value but instead expects a proof that the key is present in the map. The previous behavior is available via the map[key]? notation.The variable inclusion mechanism has been changed. Like before, when a definition mentions a variable, Lean will add it as an argument of the definition, but now in theorem bodies, variables are not included based on usage in order to ensure that changes to the proof cannot change the statement of the overall theorem. Instead, variables are only available to the proof if they have been mentioned in the theorem header or in an include command or are instance implicit and depend only on such variables. The omit command can be used to omit included variables.
See breaking changes below.
Recursive definitions
Structural recursion can now be explicitly requested using
termination_by structural x
in analogy to the existing termination_by x syntax that causes well-founded recursion to be used. #4542
#4672 fixes a bug that could lead to ill-typed terms.
The termination_by? syntax no longer forces the use of well-founded recursion, and when structural recursion is inferred, it will print the result using the termination_by structural syntax.
Mutual structural recursion is now supported. This feature supports both mutual recursion over a non-mutual data type, as well as recursion over mutual or nested data types:
mutual def Even : Nat → Prop | 0 => True | n+1 => Odd n def Odd : Nat → Prop | 0 => False | n+1 => Even n end mutual inductive A | other : B → A | empty inductive B | other : A → B | empty end mutual def A.size : A → Nat | .other b => b.size + 1 | .empty => 0 def B.size : B → Nat | .other a => a.size + 1 | .empty => 0 end inductive Tree where | node : List Tree → Tree mutual def Tree.size : Tree → Nat | node ts => Tree.list_size ts def Tree.list_size : List Tree → Nat | [] => 0 | t::ts => Tree.size t + Tree.list_size ts end
Functional induction principles are generated for these functions as well (A.size.induct, A.size.mutual_induct).
Nested structural recursion is still not supported.
PRs: #4639, #4715, #4642, #4656, #4684, #4715, #4728, #4575, #4731, #4658, #4734, #4738, #4718, #4733, #4787, #4788, #4789, #4807, #4772
#4809 makes unnecessary termination_by clauses cause warnings, not errors.
#4831 improves handling of nested structural recursion through non-recursive types.
#4839 improves support for structural recursive over inductive predicates when there are reflexive arguments.
simp tactic
Simp.Config.implicitDefEqProofs to true by default.omega tactic
decide tactic
Decidable instance.decide tactic failure. It tells you which Decidable instances it unfolded, if it get stuck on Eq.rec it gives a hint about avoiding tactics when defining Decidable instances, and if it gets stuck on Classical.choice it gives hints about classical instances being in scope. During this process, it processes Decidable.recs and matches to pin blame on a non-reducing instance.@[ext] attribute
@[ext] realize ext_iff theorems from user ext theorems. Fixes the attribute so that @[local ext] and @[scoped ext] are usable. The @[ext (iff := false)] option can be used to turn off ext_iff realization.ext_iff generation.ext_iff theorem preserve inst implicit binder types, rather than making all binder types implicit.#eval command
#eval command that prevents evaluation of terms that contain sorry. The motivation is that failing tactics, in conjunction with operations such as array accesses, can lead to the Lean process crashing. Users can use the new #eval! command to use the previous unsafe behavior. (#4829 adjusts a test.)#4447 adds #discr_tree_key and #discr_tree_simp_key commands, for helping debug discrimination tree failures. The #discr_tree_key t command prints the discrimination tree keys for a term t (or, if it is a single identifier, the type of that constant). It uses the default configuration for generating keys. The #discr_tree_simp_key command is similar to #discr_tree_key, but treats the underlying type as one of a simp lemma, that is it transforms it into an equality and produces the key of the left-hand side.
For example,
#discr_tree_key (∀ {a n : Nat}, bar a (OfNat.ofNat n))
-- bar _ (@OfNat.ofNat Nat _ _)
#discr_tree_simp_key Nat.add_assoc
-- @HAdd.hAdd Nat Nat Nat _ (@HAdd.hAdd Nat Nat Nat _ _ _) _
#4741 changes option parsing to allow user-defined options from the command line. Initial options are now re-parsed and validated after importing. Command line option assignments prefixed with weak. are silently discarded if the option name without the prefix does not exist.
Deriving handlers
Metaprogramming
unresolveNameGlobalAvoidingLocals.Meta.lambdaBoundedTelescope.Meta.withErasedFVars, to enter a context with some fvars erased from the local context.closeMainGoal, preventing users from circumventing the occurs check for tactics such as exact.Lean.Meta.PProdN module for packing and projecting nested PProds.Syntax.unsetTrailing. A consequence of this is that “go to definition” now works on the last module name in an import block (issue #4958).pp.instantiateMVars setting and changes the default value to true.ppSpace appears in a macro or elab command then it does not format with a space.#check) were overly hoverable due to pp.tagAppFns being set.match pretty printer be sensitive to pp.explicit, which makes hovering over a match in the Infoview show the underlying term.NatIntHPow Int Nat Int synthesis by rewriting it as a NatPow Int instance.UInt* and FinOptionGetElemgetElem_congr to help with rewriting indices.List and ArrayList.attach and Array.attach, #4697 upstreams List.Subset and List.Sublist and API, #4706 upstreams basic material on List.Pairwise and List.Nodup, #4720 upstreams more List.erase API, #4836 and #4837 upstream List.IsPrefix/List.IsSuffix/List.IsInfix and add Decidable instances, #4855 upstreams List.tail, List.findIdx, List.indexOf, List.countP, List.count, and List.range', #4856 upstreams more List lemmas, #4866 upstreams List.pairwise_iff_getElem, #4865 upstreams List.eraseIdx lemmas.List.replicate simp lemmas and simprocs.List.Sublist.List.Pairwise and List.Nodup.#[1,2,3,4,5][2].List.Nodup.eraseP.usize functions for array types.List.filterMapM to run left-to-right.List.Subset lemmas.Init.Data.List.Lemmas into function-specific files.List.take_takeWhile.List.head and list.getLast, #4723 for List.erase, #4742ByteArraypartial from ByteArray.toList and ByteArray.findIdx?.BitVecStd.HashMap added:Std.HashMap as a verified replacement for Lean.HashMap. See the PR for naming differences, but #4725 renames HashMap.remove to HashMap.erase.Inhabited instances.BEq argument order in hash map lemmas.bif from hash map lemmas, which is inconvenient to work with in practice.SMapSMap.foldM.BEqPartialEquivBEq, ReflBEq, EquivBEq, and LawfulHashable classes.IOIO.Process.Child.tryWait.×' syntax for PProd. Adds a delaborator for PProd and MProd values to pretty print as flattened angle bracket tuples.Antisymm class be a Prop.Init modules.Std.Data modules.not_exists.eq_iff_true_of_subsingleton.Repr instances for negative numbers for Int and Float.TC (“transitive closure”) to Relation.TransGen.List deprecations.PSigma.exists and rename it to Exists.of_psigma_prop.isDefEqStuckEx at unstuckMVar procedure, causing isDefEq to throw a stuck defeq exception if the metavariable was created in a previous level. This results in some better error messages, and it helps rw succeed in synthesizing instances (see issue #2736).elab_as_elim algorithm:Lean.Parser.Term.namedPattern (e.g. n@(n' + 1)) to report errors when used in non-pattern-matching contexts.synthAppInstances, the function responsible for synthesizing instances for the rw and apply tactics. Adds a synthesis loop to handle functions whose instances need to be synthesized in a complex order.diagnostics is enabled even if it is the only section.profileitM functions.Lean.Expr.numObjs to compute the number of allocated sub-expressions in a given expression, primarily for diagnosing performance issues.withTraceNodes to improve trace.profiler output.set_option diagnostics true” message be conditional on current setting of diagnostics.ShareCommon.shareCommon' for sharing common terms. In an example with 16 million subterms, it is 20 times faster than the old shareCommon procedure.Expr.replaceExpr preserves DAG structure in Exprs.Expr.replaceExpr.for_each use precise cache.Expr.find? and Expr.findExt? use the kernel implementations.Expr.replace use the kernel implementation.Expr.foldConsts use a precise cache.expr_eq_fn use a precise cache.ToExpr FilePath and compile_time_search_path%.const2ModIdx in finalizeImport, making it prefer the original module for a declaration when a declaration is re-declared.Nat exponentiations from evaluating. Elaborator reduction is controlled by the option exponentiation.threshold.kernel/declaration.h, making sure they reflect the current Lean 4 types.replace with a precise cache.replace_rec_fn::apply by avoiding expression copies. These copies represented about 13% of time spent in save_result in some workloads. See the same issue.trace.profiler.useHeartbeats.deprecated attributes.Syntax.hasIdent to be available earlier and shakes dependencies.Lean.Language.Lean.Types.LEAN_EXPORT for sharecommon functions.Command.Scope)Std from libleanshared to much smaller libInit_shared. This fixes the Windows build.Std in lean_initialize.shouldExport to exclude more symbols to get below Windows symbol limit. Some exceptions are added by #4884 and #4956 to support Verso.lean_is_exclusive_obj (Lean.isExclusiveUnsafe) and lean_set_external_data.#4735 improves a number of elements related to Git checkouts, cloud releases, and related error handling.
release, optRelease, extraDep are now captions in the same manner as other facets.afterReleaseSync and afterReleaseAsync now fetch optRelease rather than release.optRelease is such a job.#4608 adds draft CI workflow when creating new projects.
#4847 adds CLI options to control log levels. The --log-level=<lv> controls the minimum log level Lake should output. For instance, --log-level=error will only print errors (not warnings or info). Also, adds an analogous --fail-level option to control the minimum log level for build failures. The existing --iofail and --wfail options are respectively equivalent to --fail-level=info and --fail-level=warning.
Docs: #4853
release.lean-lang.org.pr-release to the new lakefile.lean syntax.pr-release use the correct tag name.restart-on-label CI.restart-on-label.actions/checkout and actions/upload-artifacts.actions/download-artifact.check-stage3.nightly_bump_toolchain on mathlib4 upon nightly release.tests/list_simp for retesting simp normal forms with Mathlib.For @[ext]-generated ext and ext_iff lemmas, the x and y term arguments are now implicit. Furthermore these two lemmas are now protected (#4543).
Now trace.profiler.useHearbeats is trace.profiler.useHeartbeats (#4590).
A bugfix in the structural recursion code may in some cases break existing code, when a parameter of the type of the recursive argument is bound behind indices of that type. This can usually be fixed by reordering the parameters of the function (#4672).
Now List.filterMapM sequences monadic actions left-to-right (#4820).
The effect of the variable command on proofs of theorems has been changed. Whether such section variables are accessible in the proof now depends only on the theorem signature and other top-level commands, not on the proof itself. This change ensures that
induction cannot accidentally include a section variable.The effect of variables on the theorem header as well as on other kinds of declarations is unchanged.
Specifically, section variables are included if they
include command in the current section and not subsequently mentioned in an omit statement,For porting, a new option deprecated.oldSectionVars is included to locally switch back to the old behavior.
split tactic:
split uses to generalize discriminants of matches and adds trace.split.failure trace class for diagnosing issues.rw tactic:
simp tactic:
dsimprocs for if expressions (ite and dite).OfNat numeric literals would become denormalized.dsimp configuration.simp?.implicitDefEqProofs, which will enable including rfl-theorems in proof terms.omega tactic:
bv_omega tactic:
Fin.sub in this release.#4490 sets up groundwork for a tactic index in generated documentation, as there was in Lean 3. See PR description for details.
Commands
variable command fully elaborate binders during validation, fixing an issue where some errors would be reported only at the next declaration.theorem and def declarations.theorem, def, and example, making Prop-valued examples and other definition commands elaborate like theorems.#reduce command to be able to control what gets reduced. For example, #reduce (proofs := true) (types := false) e reduces both proofs and types in the expression e. By default, neither proofs or types are reduced.#check_tactic.open _root_.<namespace>.Options
debug.byAsSorry option. Setting set_option debug.byAsSorry true causes all by ... terms to elaborate as sorry.debug.skipKernelTC option. Setting set_option debug.skipKernelTC true turns off kernel typechecking. This is meant for temporarily working around kernel performance issues, and it compromises soundness since buggy tactics may produce invalid proofs, which will not be caught if this option is set to true.#4301 adds a linter to flag situations where a local variable‘s name is one of the argumentless constructors of its type. This can arise when a user either doesn’t open a namespace or doesn't add a dot or leading qualifier, as in the following:
inductive Tree (α : Type) where | leaf | branch (left : Tree α) (val : α) (right : Tree α) def depth : Tree α → Nat | leaf => 0
With this linter, the leaf pattern is highlighted as a local variable whose name overlaps with the constructor Tree.leaf.
The linter can be disabled with set_option linter.constructorNameAsVariable false.
Additionally, the error message that occurs when a name in a pattern that takes arguments isn't valid now suggests similar names that would be valid. This means that the following definition:
def length (list : List α) : Nat := match list with | nil => 0 | cons x xs => length xs + 1
now results in the following warning:
warning: Local variable 'nil' resembles constructor 'List.nil' - write '.nil' (with a dot) or 'List.nil' to use the constructor. note: this linter can be disabled with `set_option linter.constructorNameAsVariable false`
and error:
invalid pattern, constructor or constant marked with '[match_pattern]' expected Suggestion: 'List.cons' is similar
Metaprogramming
Name.isInternalDetail function for filtering declarations using naming conventions for internal names.Other fixes or improvements
addMessageContext.pp.maxSteps option and sets the default value of pp.deepTerms to false. Together, these keep excessively large or deep terms from overwhelming the Infoview.GetElem class into GetElem and GetElem?. This enables removing Decidable instance arguments from GetElem.getElem? and GetElem.getElem!, improving their rewritability. See the docstrings for these classes for more information.ArrayListList API.List.set and List.concat API.List.filter from Batteries.@[simp] attributes.List.getElem?_eq_getElem be a simp lemma.List.replicate API.List.map.List.length_cons to use as.length + 1 instead of as.length.succ.List.filter_congr.List.bind_map.maximum?_eq_some_iff' and minimum?_eq_some_iff?.List and Array to xs[n] and xs[n]?.HashMapHashMap.insert and HashMap.erase, leading to a 40% speedup in a replace-heavy workload.OptionNatIntInt.String/CharFinFin.sub to be more performant in definitional equality checks.ProdBitVecStd libraryStd, a library situated between Init and Lean, providing functionality not in the prelude both to Lean's implementation and to external users.getBitVecValue? recognize BitVec.ofNatLt.instantiateMVars algorithm to zeta reduce let expressions while beta reducing instantiated metavariables.forEachModuleInDir to iterate over each Lean file exactly once.synthInstance?.(e :) notation.where/let rec block.findRecArg, extracting withRecArgInfo. Errors are now reported in parameter order rather than the order they are tried (non-indices are tried first). For every argument, it will say why it wasn't tried, even if the reason is obvious (e.g. a fixed prefix or is Prop-typed, etc.).PersistentEnvExtension.@[inline] attribute from NameMap.find?, which caused respecialization at each call site.trace.Elab.snapshotTree.CollectMVars and FindMVar.DecidableEq and Repr instances for intermediate structures used by the BitVec and Fin simprocs.isDefEq issue.PersistentHashMap.size.@[implemented_by] for functions defined by well-founded recursion.apply? tactic.IndPredBelow.mkBelowMatcher.#4384 deprecates inputFile and replaces it with inputBinFile and inputTextFile. Unlike inputBinFile (and inputFile), inputTextFile normalizes line endings, which helps ensure text file traces are platform-independent.
#4371 simplifies dependency resolution code.
#4439 touches up the Lake configuration DSL and makes other improvements: string literals can now be used instead of identifiers for names, avoids using French quotes in lake new and lake init templates, changes the exe template to use Main for the main module, improves the math template error if lean-toolchain fails to download, and downgrades unknown configuration fields from an error to a warning to improve cross-version compatibility.
#4496 tweaks require syntax and updates docs. Now require in TOML for a package name such as doc-gen4 does not need French quotes.
#4485 fixes a bug where package versions in indirect dependencies would take precedence over direct dependencies.
#4478 fixes a bug where Lake incorrectly included the module dynamic library in a platform-independent trace.
#4529 fixes some issues with bad import errors. A bad import in an executable no longer prevents the executable's root module from being built. This also fixes a problem where the location of a transitive bad import would not been shown. The root module of the executable now respects nativeFacets.
#4564 fixes a bug where non-identifier script names could not be entered on the CLI without French quotes.
#4566 addresses a few issues with precompiled libraries.
#4495, #4692, #4849 add a new type of require that fetches package metadata from a registry API endpoint (e.g. Reservoir) and then clones a Git package using the information provided. To require such a dependency, the new syntax is:
require <scope> / <pkg-name> [@ git <rev>] -- Examples: require "leanprover" / "doc-gen4" require "leanprover-community" / "proofwidgets" @ git "v0.0.39"
Or in TOML:
[[require]] name = "<pkg-name>" scope = "<scope>" rev = "<rev>"
Unlike with Git dependencies, Lake can make use of the richer information provided by the registry to determine the default branch of the package. This means for repositories of packages like doc-gen4 which have a default branch that is not master, Lake will now use said default branch (e.g., in doc-gen4's case, main).
Lake also supports configuring the registry endpoint via an environment variable: RESERVIOR_API_URL. Thus, any server providing a similar interface to Reservoir can be used as the registry. Further configuration options paralleling those of Cargo's Alternative Registries and Source Replacement will come in the future.
leanprover/lean4.github.event.pull_request.merge_commit_sha sometimes not being available.src/lake/lakefile.toml to avoid needing to load a version of Lake to build Lake.Char.csize is replaced by Char.utf8Size (#4357).(· == a) over (a == ·) (#3056).List and Array is xs[n] and xs[n]? rather than using functions like List.get (#4400).GetElem class has been split into two; see the docstrings for GetElem and GetElem? for more information (#4560).seal and unseal commands, which make definitions locally be irreducible or semireducible.@[irreducible] by default, which should prevent the expensive and often unfruitful unfolding of such definitions (see breaking changes below).@[incremental] attribute to mark an elaborator as supporting incremental elaboration.:= by so that stray tokens in tactic blocks do not inhibit incrementality.have tactic.set_option in theorem, theorem foo.bar, and lemma.next and if tactics.inductive Many (α : Type u) where | none : Many α | more : α → (Unit → Many α) → Many α def Many.map {α β : Type u} (f : α → β) : Many α → Many β | .none => .none | .more x xs => .more (f x) (fun _ => (xs ()).map f) #check Many.map.induct /- Many.map.induct {α β : Type u} (f : α → β) (motive : Many α → Prop) (case1 : motive Many.none) (case2 : ∀ (x : α) (xs : Unit → Many α), motive (xs ()) → motive (Many.more x xs)) : ∀ (a : Many α), motive a -/
split tacticapply tacticapply show implicit arguments in unification errors as needed. Modifies MessageData type (see breaking changes below).cases tacticx + 20000 = 20001 in cases tactic.omega tacticsimp tactic#4176 makes names of erased lemmas clickable.
#4208 adds a pretty printer for discrimination tree keys.
#4202 adds Simp.Config.index configuration option, which controls whether to use the full discrimination tree when selecting candidate simp lemmas. When index := false, only the head function is taken into account, like in Lean 3. This feature can help users diagnose tricky simp failures or issues in code from libraries developed using Lean 3 and then ported to Lean 4.
In the following example, it will report that foo is a problematic theorem.
opaque f : Nat → Nat → Nat @[simp] theorem foo : f x (x, y).2 = y := by sorry example : f a b ≤ b := by set_option diagnostics true in simp (config := { index := false }) /- [simp] theorems with bad keys foo, key: f _ (@Prod.mk ℕ ℕ _ _).2 -/
With the information above, users can annotate theorems such as foo using no_index for problematic subterms. Example:
opaque f : Nat → Nat → Nat @[simp] theorem foo : f x (no_index (x, y).2) = y := by sorry example : f a b ≤ b := by simp -- `foo` is still applied with `index := true`
#4274 prevents internal match equational theorems from appearing in simp trace.
#4177 and #4359 make simp continue even if a simp lemma does not elaborate, if the tactic state is in recovery mode.
#4341 fixes panic when applying @[simp] to malformed theorem syntax.
#4345 fixes simp so that it does not use the forward version of a user-specified backward theorem.
#4352 adds missing dsimp simplifications for fixed parameters of generated congruence theorems.
#4362 improves trace messages for simp so that constants are hoverable.
he ▸ h) try rewriting in both directions even when there is no expected type available.rfl in (h : x = y := by exact rfl)).let and have is elaborated, requiring that any tactics in the type be evaluated before proceeding, improving performance.OfNat instance, including special messages warning when the expected type of the numeral can be a proposition.grind tacticgrind_norm and grind_norm_proc attributes and @[grind_norm] theorems.grind preprocessor and core module.cases tactic to grind along with @[grind_cases] attribute to mark types that this cases tactic should automatically apply to.injection? tactic to grind.Nat.reduceLeDiff simproc.sorry term so that it does not activate the implicit lambda featurecdot and calc parsers to Lean namespace.case tactic so that it is usable in macros by having it erase macro scopes from the tag.haveId syntax.calc tactic when there is mdata or metavariables.termination_by? report unused each unused parameter as _.List and Array operations and theorems from Batteries.Inhabited instance for Subtype.@[deprecated] attributes.Char, UInt, and Fin theorems.MonadStore type classes to use semiOutParam.IsLawfulSingleton to LawfulSingleton.NatArrayArray.feraseIdx.induct.List@[simp] from List.length_pos.OptionBitVecx >>> i and x <<< i where i is a bitvector literal.(x <<< i) <<< j and (x >>> i) >>> j where i and j are natural number literals.rotateLeft/rotateRight to use modulo reduction of shift offset.<num>#<term> bitvector literal notation global.Char/StringHashMapHashMap.ofList.IOIO.Process.getCurrentDir and IO.Process.setCurrentDir for adjusting the current process's working directory.@[reducible]/@[semireducible]/@[irreducible] attributes (with local/scoped modifiers as well). Setting set_option allowUnsafeReductibility true turns this validation off.synthPendingDepth, adds maxSynthPendingDepth option with default value 1.backward.synthInstance.canonInstances to false.Lean.Elab.Command.liftCoreM and Lean.Elab.Command.liftTermElabM.Repr deriving handler be consistent between structure and inductive for how types and proofs are erased.maxHeartbeats to kernel to control “(kernel) deterministic timeout” error.FindExpr).tryCatchRuntimeEx combinator to replace catchRuntimeEx reader state.declareBuiltin to allow it to be called multiple times per declaration.tryCatchRuntimeEx uses.noConfusion applications.require commands.family_def and library_data commands.README.md to package templateslake test help page, adds help page for lake check-test, adds lake lint and tag @[lint_driver], adds support for specifying test and lint drivers from dependencies, adds testDriverArgs and lintDriverArgs options, adds support for library test drivers, makes lake check-test and lake check-lint only load the package without dependencies.lake pack and lake unpack for packing and unpacking Lake build artifacts from an archive.major.minor.patch semantic versions. Major version increments indicate breaking changes (e.g., new required fields and semantic changes to existing fields). Minor version increments (after 0.x) indicate backwards-compatible extensions (e.g., adding optional fields, removing fields). This change is backwards compatible. Lake will still successfully read old manifests with numeric versions. It will treat the numeric version N as semantic version 0.N.0. Lake will also accept manifest versions with - suffixes (e.g., x.y.z-foo) and then ignore the suffix.JobM to FetchM for backwards compatibility reasons.LogIO-to-CliM-lifting performance issues..log.json). This means logs are no longer cached on fatal errors and this ensures that an out-of-date log is not associated with an up-to-date trace. Separately, .hash file generation was changed to be more reliable as well. The .hash files are deleted as part of the build and always regenerate with --rehash.script/rebase-stage0.sh) for git rebase -i that automatically updates each stage0.full-ci label is added or removed.#guard_msgs to run tests as much as possible.pygments lexer.lean-pr-testing-NNNN Mathlib branches.lean4checker step of release checklist.pr-release CI step.While most changes could be considered to be a breaking change, this section makes special note of API changes.
Nat.zero_or and Nat.or_zero have been swapped (#4094).IsLawfulSingleton is now LawfulSingleton (#4350).BitVec literal notation is now <num>#<term> rather than <term>#<term>, and it is global rather than scoped. Use BitVec.ofNat w x rather than x#w when x is a not a numeric literal (0d3051).BitVec.rotateLeft and BitVec.rotateRight now take the shift modulo the bitwidth (#4229).List.length_pos (#4172), Option.bind_eq_some (#4314).let and have (both the expressions and tactics) may fail to elaborate due to new restrictions on what sorts of elaboration problems may be postponed (#4096). In particular, tactics embedded in the type will no longer make use of the type of value in expressions such as let x : type := value; body.@[irreducible] by default (#4061). Existing proofs that hold by definitional equality (e.g. rfl) can be rewritten to explicitly unfold the function definition (using simp, unfold, rw), or the recursive function can be temporarily made semireducible (using unseal f in before the command), or the function definition itself can be marked as @[semireducible] to get the previous behavior.The MessageData.ofPPFormat constructor has been removed. Its functionality has been split into two:
MessageData.lazy;Format or FormatWithInfos, use MessageData.ofFormatWithInfos.An example migration can be found in #3929.
The MessageData.ofFormat constructor has been turned into a function. If you need to inspect MessageData, you can pattern-match on MessageData.ofFormatWithInfos.
Functional induction principles. #3432, #3620, #3754, #3762, #3738, #3776, #3898.
Derived from the definition of a (possibly mutually) recursive function, a functional induction principle is created that is tailored to proofs about that function.
For example from:
def ackermann : Nat → Nat → Nat | 0, m => m + 1 | n+1, 0 => ackermann n 1 | n+1, m+1 => ackermann n (ackermann (n + 1) m)
we get
ackermann.induct (motive : Nat → Nat → Prop) (case1 : ∀ (m : Nat), motive 0 m) (case2 : ∀ (n : Nat), motive n 1 → motive (Nat.succ n) 0) (case3 : ∀ (n m : Nat), motive (n + 1) m → motive n (ackermann (n + 1) m) → motive (Nat.succ n) (Nat.succ m)) (x x : Nat) : motive x x
It can be used in the induction tactic using the using syntax:
induction n, m using ackermann.induct
The termination checker now recognizes more recursion patterns without an explicit termination_by. In particular the idiom of counting up to an upper bound, as in
def Array.sum (arr : Array Nat) (i acc : Nat) : Nat :=
if _ : i < arr.size then
Array.sum arr (i+1) (acc + arr[i])
else
acc
is recognized without having to say termination_by arr.size - i.
#3629, #3655, #3747: Adds @[induction_eliminator] and @[cases_eliminator] attributes to be able to define custom eliminators for the induction and cases tactics, replacing the @[eliminator] attribute. Gives custom eliminators for Nat so that induction and cases put goal states into terms of 0 and n + 1 rather than Nat.zero and Nat.succ n. Added option tactic.customEliminators to control whether to use custom eliminators. Added a hack for rcases/rintro/obtain to use the custom eliminator for Nat.
Shorter instances names. There is a new algorithm for generating names for anonymous instances. Across Std and Mathlib, the median ratio between lengths of new names and of old names is about 72%. With the old algorithm, the longest name was 1660 characters, and now the longest name is 202 characters. The new algorithm's 95th percentile name length is 67 characters, versus 278 for the old algorithm. While the new algorithm produces names that are 1.2% less unique, it avoids cross-project collisions by adding a module-based suffix when it does not refer to declarations from the same “project” (modules that share the same root). #3089 and #3934.
8d2adf Importing two different files containing proofs of the same theorem is no longer considered an error. This feature is particularly useful for theorems that are automatically generated on demand (e.g., equational theorems).
84b091 Lean now generates an error if the type of a theorem is not a proposition.
Definition transparency. 47a343. @[reducible], @[semireducible], and @[irreducible] are now scoped and able to be set for imported declarations.
simp/dsimp
dsimpdsimproc command to define defeq-preserving simplification procedures.dsimp normalize raw nat literals as OfNat.ofNat applications.simp correctly handle OfScientific.ofScientific literals.dsimp? report used simprocs.simp for non-recursive definitions.simp from breaking Char literals.Nat instances matching to be more lenient.simp configuration options.omega
rfl
#3719 upstreams the rw? tactic, with fixes and improvements in #3783, #3794, #3911.
conv
#guard_msgs
⏎ character.#guard_msgs command now has options to change whitespace normalization and sensitivity to message ordering. For example, #guard_msgs (whitespace := lax) in cmd collapses whitespace before checking messages, and #guard_msgs (ordering := sorted) in cmd sorts the messages in lexicographic order before checking.#guard_msgs.set_option guard_msgs.diff true. Depending on user feedback, this option may default to true in a future version of Lean.do notation
(<- ...) out of a pure if ... then ... else ...Lazy discrimination trees
LazyDiscrTree that could lead to cache poisoning.LazyDiscrTree handling for exact?/apply?.exact?/apply? functionality into LazyDiscrTree.rw? and LazyDiscrTree.#3590 adds inductive.autoPromoteIndices option to be able to disable auto promotion of indices in the inductive command.
Miscellaneous bug fixes and improvements
cache and dischargeDepth fields in Lean.Meta.Simp.Result.mkEqSymm.elabTermEnsuringType respect errToSorry, improving error recovery of the have tactic.noncomputable unsafe definitions, for deferring implementations until later.Ord derive handler for indexed inductive types with unused alternatives.Ord instances.rfl error message.universe, variable, namespace, etc. require that their argument appear in a later column. Commands that can optionally parse an ident or parse any number of idents generally should require that the ident use colGt. This keeps typos in commands from being interpreted as identifiers.split tactic be used for writing code.induction tactic for with clauses of the form | cstr a b c => ?_.withSetOptionIn combinator.trace.Elab.syntax option.attribute command.@[builtin_term_parser].solveByElim handles symm lemmas, making exact?/apply? usable again.@[deprecated] attribute, adding (since := "<date>") field.#print command show structure fields.exact?% behave like by exact? rather than by apply?.he ▸ h notation more predictable.decreasing_trivial macros.binop% and binrel% expression tree elaborators.Docs: #3748, #3796, #3800, #3874, #3863, #3862, #3891, #3873, #3908, #3872.
import auto-completions.@[pp_using_anonymous_constructor] to make structures pretty print as ⟨x, y, z⟩ rather than as {a := x, b := y, c := z}. This attribute is applied to Sigma, PSigma, PProd, Subtype, And, and Fin.B extends A, then { toA := { x := 1 }, y := 2 } now pretty prints as { x := 1, y := 2 }. Setting option pp.structureInstances.flatten to false turns this off.pp.structureProjections is renamed to pp.fieldNotation, and there is now a suboption pp.fieldNotation.generalized to enable pretty printing function applications using generalized field notation (defaults to true). Field notation can be disabled on a function-by-function basis using the @[pp_nodot] attribute. The notation is not used for theorems.pp.fieldNotation.generalizeddelabConstWithSignature (used by #check) have the ability to put arguments “after the colon” to avoid printing inaccessible names.pp.mvars (default: true) and pp.mvars.withType (default: false). When pp.mvars is false, expression metavariables pretty print as ?_ and universe metavariables pretty print as _. When pp.mvars.withType is true, expression metavariables pretty print with a type ascription. These can be set when using #guard_msgs to make tests not depend on the particular names of metavariables.match expressions in the Infoview reliably show the correct term.Bool/Prop
Nat
Int
UInts
Array and Subarray
List
@[csimp] lemmas.BitVec
String
IO
IO.getTaskState which returns whether a task is finished, actively running, or waiting on other Tasks to finish.Refactors
Init.Data.Nat and Init.Data.Int.Init.Omega.Int.Std.Data.Nat and #3635 upstreams Std.Data.Int.omega.GetElem interface with getElem! and getElem? to simplify containers like RBMap.Option.toMonad (see breaking changes below).lexOrd with compareLex.Other fixes or improvements
Quotient.sound be a theorem.System.FilePath.parent in the case of absolute paths.ByteArray.toUInt64LE! and ByteArray.toUInt64BE! were swapped.HashMap.insertIfNew, HashSet.erase, and HashMap.erase. The HashMap.insertIfNew fix improves import performance.Parsec.many*Core.FS.Stream.isTty field.Option.toBool in favor of Option.isSome.Data.List.Init and Data.Array.Init material from Std.ac_rfl work without Mathlib.Fin.induction to use structural induction.reduceLeDiff simproc.IO.TaskState and IO.getTaskState to get the task from the Lean runtime's task manager.Docs: #3615, #3664, #3707, #3734, #3868, #3861, #3869, #3858, #3856, #3857, #3867, #3864, #3860, #3859, #3871, #3919.
Nat.rec expressions.isDefEq performance issue, now trying structure eta after lazy delta reduction..yesWithDeltaI behavior to prevent increasing transparency level when reducing projections.isDefEq.isDefEq for constraints of the form t.i =?= s.i.isDefEqProj.u =?= max u ?v using ?v = u. These approximations are only applied when universe constraints cannot be postponed anymore.isDefEqProj during typeclass resolution.backward.isDefEq.lazyProjDelta and backward.isDefEq.lazyWhnfCore backwards compatibility flags..eq_<idx> instead of ._eq_<idx>, and .eq_def instead of ._unfold. (See breaking changes below.) #3675 adds a mechanism to reserve names. #3803 fixes reserved name resolution inside namespaces and fixes handling of matcher declarations and equation lemmas.defs if they are not proofs.structures be theorems.extern.Lean.Meta.evalNat.Fix/GuessLex/FunInd in the ArgsPacker module.String to Name (see breaking changes below).lines field from FileMap.throwTacticEx optional.set_option diagnostics true for diagnostic counters. Tracks number of unfolded declarations, instances, reducible declarations, used instances, recursor reductions, isDefEq heuristic applications, among others. This option is suggested in exceptional situations, such as at deterministic timeout and maximum recursion depth.simp.set_option diagnostics true in <tactic> and set_option diagnostics true in <term>.trace.profiler can now export to Firefox Profiler.@[builtin_doc] attribute to make docs and location of a declaration available as a builtin.lean --json CLI option to print messages as JSON.test_extern command.FindExpr.IO.Promise.resolve.MoveFileEx on Windows.reset bug in ResetReuse transformation.interpreter copy constructor to avoid potential memory safety issues.TOML Lake configurations. #3298, #4104.
Lake packages can now use TOML as a alternative configuration file format instead of Lean. If the default lakefile.lean is missing, Lake will also look for a lakefile.toml. The TOML version of the configuration supports a restricted set of the Lake configuration options, only including those which can easily mapped to a TOML data structure. The TOML syntax itself fully compiles with the TOML v1.0.0 specification.
As part of the introduction of this new feature, we have been helping maintainers of some major packages within the ecosystem switch to this format. For example, the following is Aesop's new lakefile.toml:
leanprover-community/aesop/lakefile.toml
name = "aesop" defaultTargets = ["Aesop"] testRunner = "test" precompileModules = false [[require]] name = "batteries" git = "https://github.com/leanprover-community/batteries" rev = "main" [[lean_lib]] name = "Aesop" [[lean_lib]] name = "AesopTest" globs = ["AesopTest.+"] leanOptions = {linter.unusedVariables = false} [[lean_exe]] name = "test" srcDir = "scripts"
To assist users who wish to transition their packages between configuration file formats, there is also a new lake translate-config command for migrating to/from TOML.
Running lake translate-config toml will produce a lakefile.toml version of a package's lakefile.lean. Any configuration options unsupported by the TOML format will be discarded during translation, but the original lakefile.lean will remain so that you can verify the translation looks good before deleting it.
Build progress overhaul. #3835, #4115, #4127, #4220, #4232, #4236.
Builds are now managed by a top-level Lake build monitor, this makes the output of Lake builds more standardized and enables producing prettier and more configurable progress reports.
As part of this change, job isolation has improved. Stray I/O and other build related errors in custom targets are now properly isolated and caught as part of their job. Import errors no longer cause Lake to abort the entire build and are instead localized to the build jobs of the modules in question.
Lake also now uses ANSI escape sequences to add color and produce progress lines that update in-place; this can be toggled on and off using --ansi / --no-ansi.
--wfail and --iofail options have been added that causes a build to fail if any of the jobs log a warning (--wfail) or produce any output or log information messages (--iofail). Unlike some other build systems, these options do NOT convert these logs into errors, and Lake does not abort jobs on such a log (i.e., dependent jobs will still continue unimpeded).
lake test. #3779.
Lake now has a built-in test command which will run a script or executable labelled @[test_runner] (in Lean) or defined as the testRunner (in TOML) in the root package.
Lake also provides a lake check-test command which will exit with code 0 if the package has a properly configured test runner or error with 1 otherwise.
lake lean. #3793.
The new command lake lean <file> [-- <args...>] functions like lake env lean <file> <args...>, except that it builds the imports of file before running lean. This makes it very useful for running test or example code that imports modules that are not guaranteed to have been built beforehand.
Miscellaneous bug fixes and improvements
LEAN_GITHASH environment variable to override the detected Git hash for Lean when computing traces, useful for testing custom builds of Lean.std-to-batteries rename.Docs: #3704.
#3600 runs nix-ci more uniformly.
#3612 avoids argument limits when building on Windows.
#3682 builds Lean's .o files in parallel to rest of core.
#3601 changes the way Lean is built on Windows (see breaking changes below). As a result, Lake now dynamically links executables with supportInterpreter := true on Windows to libleanshared.dll and libInit_shared.dll. Therefore, such executables will not run unless those shared libraries are co-located with the executables or part of PATH. Running the executable via lake exe will ensure these libraries are part of PATH.
In a related change, the signature of the nativeFacets Lake configuration options has changed from a static Array to a function (shouldExport : Bool) → Array. See its docstring or Lake's README for further details on the changed option.
#3690 marks “Build matrix complete” as canceled if the build is canceled.
#3700, #3702, #3701, #3834, #3923: fixes and improvements for std and mathlib CI.
#3712 fixes nix build . on macOS.
#3717 replaces shell.nix in devShell with flake.nix.
#3971 prevents stage0 changes via the merge queue.
#3979 adds handling for changes-stage0 label.
#3952 adds a script to summarize GitHub issues.
18a699 fixes asan linking
Due to the major Lake build refactor, code using the affected parts of the Lake API or relying on the previous output format of Lake builds is likely to have been broken. We have tried to minimize the breakages and, where possible, old definitions have been marked @[deprecated] with a reference to the new alternative.
Executables configured with supportInterpreter := true on Windows should now be run via lake exe to function properly.
Automatically generated equational theorems are now named using suffix .eq_<idx> instead of ._eq_<idx>, and .eq_def instead of ._unfold. Example:
def fact : Nat → Nat
| 0 => 1
| n+1 => (n+1) * fact n
theorem ex : fact 0 = 1 := by unfold fact; decide
#check fact.eq_1
-- fact.eq_1 : fact 0 = 1
#check fact.eq_2
-- fact.eq_2 (n : Nat) : fact (Nat.succ n) = (n + 1) * fact n
#check fact.eq_def
/-
fact.eq_def :
∀ (x : Nat),
fact x =
match x with
| 0 => 1
| Nat.succ n => (n + 1) * fact n
-/
The coercion from String to Name was removed. Previously, it was Name.mkSimple, which does not separate strings at dots, but experience showed that this is not always the desired coercion. For the previous behavior, manually insert a call to Name.mkSimple.
The Subarray fields as, h₁ and h₂ have been renamed to array, start_le_stop, and stop_le_array_size, respectively. This more closely follows standard Lean conventions. Deprecated aliases for the field projections were added; these will be removed in a future release.
The change to the instance name algorithm (described above) can break projects that made use of the auto-generated names.
Option.toMonad has been renamed to Option.getM and the unneeded [Monad m] instance argument has been removed.
simp and rw now use instance arguments found by unification, rather than always resynthesizing. For backwards compatibility, the original behaviour is available via set_option tactic.skipAssignedInstances false. #3507 and #3509.
When the pp.proofs is false, now omitted proofs use ⋯ rather than _, which gives a more helpful error message when copied from the Infoview. The pp.proofs.threshold option lets small proofs always be pretty printed. #3241.
pp.proofs.withType is now set to false by default to reduce noise in the info view.
The pretty printer for applications now handles the case of over-application itself when applying app unexpanders. In particular, the | `($_ $a $b $xs*) => `(($a + $b) $xs*) case of an app_unexpander is no longer necessary. #3495.
New simp (and dsimp) configuration option: zetaDelta. It is false by default. The zeta option is still true by default, but their meaning has changed.
zeta := true, simp and dsimp reduce terms of the form let x := val; e[x] into e[val].zetaDelta := true, simp and dsimp will expand let-variables in the context. For example, suppose the context contains x := val. Then, any occurrence of x is replaced with val.See issue #2682 for additional details. Here are some examples:
example (h : z = 9) : let x := 5; let y := 4; x + y = z := by
intro x
simp
/-
New goal:
h : z = 9; x := 5 |- x + 4 = z
-/
rw [h]
example (h : z = 9) : let x := 5; let y := 4; x + y = z := by
intro x
-- Using both `zeta` and `zetaDelta`.
simp (config := { zetaDelta := true })
/-
New goal:
h : z = 9; x := 5 |- 9 = z
-/
rw [h]
example (h : z = 9) : let x := 5; let y := 4; x + y = z := by
intro x
simp [x] -- asks `simp` to unfold `x`
/-
New goal:
h : z = 9; x := 5 |- 9 = z
-/
rw [h]
example (h : z = 9) : let x := 5; let y := 4; x + y = z := by
intro x
simp (config := { zetaDelta := true, zeta := false })
/-
New goal:
h : z = 9; x := 5 |- let y := 4; 5 + y = z
-/
rw [h]
When adding new local theorems to simp, the system assumes that the function application arguments have been annotated with no_index. This modification, which addresses issue #2670, restores the Lean 3 behavior that users expect. With this modification, the following examples are now operational:
example {α β : Type} {f : α × β → β → β} (h : ∀ p : α × β, f p p.2 = p.2)
(a : α) (b : β) : f (a, b) b = b := by
simp [h]
example {α β : Type} {f : α × β → β → β}
(a : α) (b : β) (h : f (a,b) (a,b).2 = (a,b).2) : f (a, b) b = b := by
simp [h]
In both cases, h is applicable because simp does not index f-arguments anymore when adding h to the simp-set. It's important to note, however, that global theorems continue to be indexed in the usual manner.
Improved the error messages produced by the decide tactic. #3422
Improved auto-completion performance. #3460
Improved initial language server startup performance. #3552
Changed call hierarchy to sort entries and strip private header from names displayed in the call hierarchy. #3482
There is now a low-level error recovery combinator in the parsing framework, primarily intended for DSLs. #3413
You can now write termination_by? after a declaration to see the automatically inferred termination argument, and turn it into a termination_by … clause using the “Try this” widget or a code action. #3514
A large fraction of Std has been moved into the Lean repository. This was motivated by:
ext, by_cases, change at, norm_cast, rcases, simpa, simp?, omega, and exact? available to all users of Lean, without imports.import Std.Nat, Int, Fin (and variants such as UInt64), List, Array, and BitVec as we begin making the APIs and simp normal forms for these types more complete and consistent.RBMap) and utilities such as basic IO. While we have achieved most of our initial aims in v4.7.0-rc1, some upstreaming will continue over the coming months.The / and % notations in Int now use Int.ediv and Int.emod (i.e. the rounding conventions have changed). Previously Std overrode these notations, so this is no change for users of Std. There is now kernel support for these functions. #3376.
omega, our integer linear arithmetic tactic, is now available in the core language.
bv_omega which can solve goals about BitVec which naturally translate into linear arithmetic problems. #3435.omega now has support for Fin #3427, the <<< operator #3433.omega was modified to no longer identify atoms up to definitional equality (so in particular it can no longer prove id x ≤ x). #3525. This may cause some regressions. We plan to provide a general purpose preprocessing tactic later, or an omega! mode.omega is now invoked in Lean's automation for termination proofs #3503 as well as in array indexing proofs #3515. This automation will be substantially revised in the medium term, and while omega does help automate some proofs, we plan to make this much more robust.The library search tactics exact? and apply? that were originally in Mathlib are now available in Lean itself. These use the implementation using lazy discrimination trees from Std, and thus do not require a disk cache but have a slightly longer startup time. The order used for selection lemmas has changed as well to favor goals purely based on how many terms in the head pattern match the current goal.
The solve_by_elim tactic has been ported from Std to Lean so that library search can use it.
New #check_tactic and #check_simp commands have been added. These are useful for checking tactics (particularly simp) behave as expected in test suites.
Previously, app unexpanders would only be applied to entire applications. However, some notations produce functions, and these functions can be given additional arguments. The solution so far has been to write app unexpanders so that they can take an arbitrary number of additional arguments. However this leads to misleading hover information in the Infoview. For example, while HAdd.hAdd f g 1 pretty prints as (f + g) 1, hovering over f + g shows f. There is no way to fix the situation from within an app unexpander; the expression position for HAdd.hAdd f g is absent, and app unexpanders cannot register TermInfo.
This commit changes the app delaborator to try running app unexpanders on every prefix of an application, from longest to shortest prefix. For efficiency, it is careful to only try this when app delaborators do in fact exist for the head constant, and it also ensures arguments are only delaborated once. Then, in (f + g) 1, the f + g gets TermInfo registered for that subexpression, making it properly hoverable.
Breaking changes:
Lean.withTraceNode and variants got a stronger MonadAlwaysExcept assumption to fix trace trees not being built on elaboration runtime exceptions. Instances for most elaboration monads built on EIO Exception should be synthesized automatically.match ... with. and fun. notations previously in Std have been replaced by nomatch ... and nofun. #3279 and #3286Other improvements:
simp:match expressions:termination_by error messages #3255rename_i in macros, fixes #3553 #3581generalize, fixes #3524 #3575add_decl_doc should check that declarations are local #3311Lake fixes:
Add custom simplification procedures (aka simprocs) to simp. Simprocs can be triggered by the simplifier on a specified term-pattern. Here is an small example:
import Lean.Meta.Tactic.Simp.BuiltinSimprocs.Nat def foo (x : Nat) : Nat := x + 10 /-- The `simproc` `reduceFoo` is invoked on terms that match the pattern `foo _`. -/ simproc reduceFoo (foo _) := /- A term of type `Expr → SimpM Step -/ fun e => do /- The `Step` type has three constructors: `.done`, `.visit`, `.continue`. * The constructor `.done` instructs `simp` that the result does not need to be simplified further. * The constructor `.visit` instructs `simp` to visit the resulting expression. * The constructor `.continue` instructs `simp` to try other simplification procedures. All three constructors take a `Result`. The `.continue` constructor may also take `none`. `Result` has two fields `expr` (the new expression), and `proof?` (an optional proof). If the new expression is definitionally equal to the input one, then `proof?` can be omitted or set to `none`. -/ /- `simp` uses matching modulo reducibility. So, we ensure the term is a `foo`-application. -/ unless e.isAppOfArity ``foo 1 do return .continue /- `Nat.fromExpr?` tries to convert an expression into a `Nat` value -/ let some n ← Nat.fromExpr? e.appArg! | return .continue return .done { expr := Lean.mkNatLit (n+10) }
We disable simprocs support by using the command set_option simprocs false. This command is particularly useful when porting files to v4.6.0. Simprocs can be scoped, manually added to simp commands, and suppressed using -. They are also supported by simp?. simp only does not execute any simproc. Here are some examples for the simproc defined above.
example : x + foo 2 = 12 + x := by set_option simprocs false in /- This `simp` command does not make progress since `simproc`s are disabled. -/ fail_if_success simp simp_arith example : x + foo 2 = 12 + x := by /- `simp only` must not use the default simproc set. -/ fail_if_success simp only simp_arith example : x + foo 2 = 12 + x := by /- `simp only` does not use the default simproc set, but we can provide simprocs as arguments. -/ simp only [reduceFoo] simp_arith example : x + foo 2 = 12 + x := by /- We can use `-` to disable `simproc`s. -/ fail_if_success simp [-reduceFoo] simp_arith
The command register_simp_attr <id> now creates a simp and a simproc set with the name <id>. The following command instructs Lean to insert the reduceFoo simplification procedure into the set my_simp. If no set is specified, Lean uses the default simp set.
simproc [my_simp] reduceFoo (foo _) := ...
The syntax of the termination_by and decreasing_by termination hints is overhauled:
mutual block.where clause, the termination_by and decreasing_by for that function come before the where. The functions in the where clause can have their own termination hints, each following the corresponding definition.termination_by clause can only bind “extra parameters”, that are not already bound by the function header, but are bound in a lambda (:= fun x y z =>) or in patterns (| x, n + 1 => …). These extra parameters used to be understood as a suffix of the function parameters; now it is a prefix.Migration guide: In simple cases just remove the function name, and any variables already bound at the header.
def foo : Nat → Nat → Nat := … -termination_by foo a b => a - b +termination_by a b => a - b
or
def foo : Nat → Nat → Nat := … -termination_by _ a b => a - b +termination_by a b => a - b
If the parameters are bound in the function header (before the :), remove them as well:
def foo (a b : Nat) : Nat := … -termination_by foo a b => a - b +termination_by a - b
Else, if there are multiple extra parameters, make sure to refer to the right ones; the bound variables are interpreted from left to right, no longer from right to left:
def foo : Nat → Nat → Nat → Nat | a, b, c => … -termination_by foo b c => b +termination_by a b => b
In the case of a mutual block, place the termination arguments (without the function name) next to the function definition:
-mutual -def foo : Nat → Nat → Nat := … -def bar : Nat → Nat := … -end -termination_by - foo a b => a - b - bar a => a +mutual +def foo : Nat → Nat → Nat := … +termination_by a b => a - b +def bar : Nat → Nat := … +termination_by a => a +end
Similarly, if you have (mutual) recursion through where or let rec, the termination hints are now placed directly after the function they apply to:
-def foo (a b : Nat) : Nat := … - where bar (x : Nat) : Nat := … -termination_by - foo a b => a - b - bar x => x +def foo (a b : Nat) : Nat := … +termination_by a - b + where + bar (x : Nat) : Nat := … + termination_by x -def foo (a b : Nat) : Nat := - let rec bar (x : Nat) : Nat := … - … -termination_by - foo a b => a - b - bar x => x +def foo (a b : Nat) : Nat := + let rec bar (x : Nat) : Nat := … + termination_by x + … +termination_by a - b
In cases where a single decreasing_by clause applied to multiple mutually recursive functions before, the tactic now has to be duplicated.
The semantics of decreasing_by changed; the tactic is applied to all termination proof goals together, not individually.
This helps when writing termination proofs interactively, as one can focus each subgoal individually, for example using ·. Previously, the given tactic script had to work for all goals, and one had to resort to tactic combinators like first:
def foo (n : Nat) := … foo e1 … foo e2 … -decreasing_by -simp_wf -first | apply something_about_e1; … - | apply something_about_e2; … +decreasing_by +all_goals simp_wf +· apply something_about_e1; … +· apply something_about_e2; …
To obtain the old behaviour of applying a tactic to each goal individually, use all_goals:
def foo (n : Nat) := … -decreasing_by some_tactic +decreasing_by all_goals some_tactic
In the case of mutual recursion each decreasing_by now applies to just its function. If some functions in a recursive group do not have their own decreasing_by, the default decreasing_tactic is used. If the same tactic ought to be applied to multiple functions, the decreasing_by clause has to be repeated at each of these functions.
Modify InfoTree.context to facilitate augmenting it with partial contexts while elaborating a command. This breaks backwards compatibility with all downstream projects that traverse the InfoTree manually instead of going through the functions in InfoUtils.lean, as well as those manually creating and saving InfoTrees. See PR #3159 for how to migrate your code.
Add language server support for call hierarchy requests (PR #3082). The change to the .ilean format in this PR means that projects must be fully rebuilt once in order to generate .ilean files with the new format before features like “find references” work correctly again.
Structure instances with multiple sources (for example {a, b, c with x := 0}) now have their fields filled from these sources in strict left-to-right order. Furthermore, the structure instance elaborator now aggressively use sources to fill in subobject fields, which prevents unnecessary eta expansion of the sources, and hence greatly reduces the reliance on costly structure eta reduction. This has a large impact on mathlib, reducing total CPU instructions by 3% and enabling impactful refactors like leanprover-community/mathlib4#8386 which reduces the build time by almost 20%. See PR #2478 and RFC #2451.
Add pretty printer settings to omit deeply nested terms (pp.deepTerms false and pp.deepTerms.threshold) (PR #3201)
Add pretty printer options pp.numeralTypes and pp.natLit. When pp.numeralTypes is true, then natural number literals, integer literals, and rational number literals are pretty printed with type ascriptions, such as (2 : Rat), (-2 : Rat), and (-2 / 3 : Rat). When pp.natLit is true, then raw natural number literals are pretty printed as nat_lit 2. PR #2933 and RFC #3021.
Lake updates:
Other improvements:
intro be aware of let_fun #3115rw #3121mkCongrArg calls in proofs generated by simp #3203induction using followed by a general term #3188let #3060, fixing #3065swap! should return a, not `default`` #3197, fixing #3196BEq on structure with Prop-fields #3191, fixing #3140casesOnApp/matcherApp #3176, fixing #3175deriving only deriving the first declaration for some handlers #3058, fixing #3057cases h : ... #3084Modify the lexical syntax of string literals to have string gaps, which are escape sequences of the form "\" newline whitespace*. These have the interpretation of an empty string and allow a string to flow across multiple lines without introducing additional whitespace. The following is equivalent to "this is a string".
"this is \ a string"
Add raw string literal syntax. For example, r"\n" is equivalent to "\\n", with no escape processing. To include double quote characters in a raw string one can add sufficiently many # characters before and after the bounding "s, as in r#"the "the" is in quotes"# for "the \"the\" is in quotes". PR #2929 and issue #1422.
The low-level termination_by' clause is no longer supported.
Migration guide: Use termination_by instead, e.g.:
-termination_by' measure (fun ⟨i, _⟩ => as.size - i) +termination_by i _ => as.size - i
If the well-founded relation you want to use is not the one that the WellFoundedRelation type class would infer for your termination argument, you can use WellFounded.wrap from the std library to explicitly give one:
-termination_by' ⟨r, hwf⟩ +termination_by x => hwf.wrap x
Support snippet edits in LSP TextEdits. See Lean.Lsp.SnippetString for more details.
Deprecations and changes in the widget API.
Widget.UserWidgetDefinition is deprecated in favour of Widget.Module. The annotation @[widget] is deprecated in favour of @[widget_module]. To migrate a definition of type UserWidgetDefinition, remove the name field and replace the type with Widget.Module. Removing the name results in a title bar no longer being drawn above your panel widget. To add it back, draw it as part of the component using <details open=true><summary class='mv2 pointer'>{name}</summary>{rest_of_widget}</details>. See an example migration here.show_panel_widgets allows displaying always-on and locally-on panel widgets.RpcEncodable widget props can now be stored in the infotree.If no usable lexicographic order can be found automatically for a termination proof, explain why. See feat: GuessLex: if no measure is found, explain why.
Option to print inferred termination argument. With set_option showInferredTerminationBy true you will get messages like
Inferred termination argument: termination_by ackermann n m => (sizeOf n, sizeOf m)
for automatically generated termination_by clauses.
More detailed error messages for invalid mutual blocks.
Multiple improvements to the output of simp? and simp_all?.
Tactics with withLocation * no longer fail if they close the main goal.
Implementation of a test_extern command for writing tests for @[extern] and @[implemented_by] functions. Usage is
import Lean.Util.TestExtern test_extern Nat.add 17 37
The head symbol must be the constant with the @[extern] or @[implemented_by] attribute. The return type must have a DecidableEq instance.
Bug fixes for #2853, #2953, #2966, #2971, #2990, #3094.
Bug fix for eager evaluation of default value in Option.getD. Avoid panic in leanPosToLspPos when file source is unavailable. Improve short-circuiting behavior for List.all and List.any.
Several Lake bug fixes: #3036, #3064, #3069.
Lake and the language server now support per-package server options using the moreServerOptions config field, as well as options that apply to both the language server and lean using the leanOptions config field. Setting either of these fields instead of moreServerArgs ensures that viewing files from a dependency uses the options for that dependency. Additionally, moreServerArgs is being deprecated in favor of the moreGlobalServerArgs field. See PR #2858.
A Lakefile with the following deprecated package declaration:
def moreServerArgs := #[ "-Dpp.unicode.fun=true" ] def moreLeanArgs := moreServerArgs package SomePackage where moreServerArgs := moreServerArgs moreLeanArgs := moreLeanArgs
... can be updated to the following package declaration to use per-package options:
package SomePackage where leanOptions := #[⟨`pp.unicode.fun, true⟩]
Bug fixes for #2628, #2883, #2810, #2925, and #2914.
Lake:
lake init . and a bare lake init and will now use the current directory as the package name. #2890lake new and lake init will now produce errors on invalid package names such as .., foo/bar, Init, Lean, Lake, and Main. See issue #2637 and PR #2890.lean_lib no longer converts its name to upper camel case (e.g., lean_lib bar will include modules named bar.* rather than Bar.*). See issue #2567 and PR #2889.lake new 123-hello and import «123Hello» now work correctly). See issue #2865 and PR #2889.lakefile.olean) to include only those relevant to Lake's workspace loading process. This resolves segmentation faults caused by environment extension type mismatches (e.g., when defining custom elaborators via elab in configurations). See issue #2632 and PR #2896.math template has been simplified. See PR #2930.lake exe <target> now parses target like a build target (as the help text states it should) rather than as a basic name. For example, lake exe @mathlib/runLinter should now work. See PR #2932.lake new foo.bar [std] now generates executables named foo-bar and lake new foo.bar exe properly creates foo/bar.lean. See PR #2932.findModule?. See PR #2937.simp [f] does not unfold partial applications of f anymore. See issue #2042. To fix proofs affected by this change, use unfold f or simp (config := { unfoldPartialApp := true }) [f].
By default, simp will no longer try to use Decidable instances to rewrite terms. In particular, not all decidable goals will be closed by simp, and the decide tactic may be useful in such cases. The decide simp configuration option can be used to locally restore the old simp behavior, as in simp (config := {decide := true}); this includes using Decidable instances to verify side goals such as numeric inequalities.
Many bug fixes:
Decidable instances very slow when using cases tacticsimp not rewriting in bindersimp unfolding let even with zeta := false optionsimp (with beta/zeta disabled) and discrimination treesrw ... at hdsimp doesn't use rfl theorems which consist of an unapplied constantdsimp does not close reflexive equality goals if they are wrapped in metadatarw [h] uses h from the environment in preference to h from the local contextwithAssignableSyntheticOpaque for assumption tacticCancel outstanding tasks on document edit in the language server.
Lake:
lake new MyProject mathpostUpdate? configuration option to a post_update declaration. See the post_update syntax docstring for more information on the new syntax.:= syntax for configuration declarations (i.e., package, lean_lib, and lean_exe) has been deprecated. For example, package foo := {...} is deprecated.LAKE_PKG_URL_MAPbuild), default packages directory (e.g., lake-packages), and the compiled configuration (e.g., lakefile.olean) into a new dedicated directory for Lake outputs, .lake. The cloud release build archives are also stored here, fixing #2713.manifestFile field of a package configuration.lakefile.olean compatibility (see #2842 for more details).Environment.mk and Environment.add private, and add replay as a safer alternative.IO.Process.output no longer inherits the standard input of the caller.match reduction.DecidableEq now handles mutual inductive types.postUpdate? package configuration option. Used by a package to specify some code which should be run after a successful lake update of the package or one of its downstream dependencies. (lake#185)refine e now replaces the main goal with metavariables which were created during elaboration of e and no longer captures pre-existing metavariables that occur in e (#2502).withCollectingNewGoalsFrom, which also affects elabTermWithHoles, refine', calc (tactic), and specialize. Likewise, all of these now only include newly-created metavariables in their output.e were returned inconsistently in different edge cases, causing duplicated goals in the infoview (issue #2495), erroneously closed goals (issue #2434), and unintuitive behavior due to refine e capturing previously-created goals appearing unexpectedly in e (no issue; see PR).The error positioning on missing tokens has been improved. In particular, this should make it easier to spot errors in incomplete tactic proofs.
After elaborating a configuration file, Lake will now cache the configuration to a lakefile.olean. Subsequent runs of Lake will import this OLean instead of elaborating the configuration file. This provides a significant performance improvement (benchmarks indicate that using the OLean cuts Lake's startup time in half), but there are some important details to keep in mind:
lakefile.lean or lean-toolchain. You can also force a reconfigure by passing the new --reconfigure / -R option to lake.-K) will be fixed at the moment of elaboration. Setting these options when lake is using the cached configuration will have no effect. To change options, run lake with -R / --reconfigure.lakefile.olean is a local configuration and should not be committed to Git. Therefore, existing Lake packages need to add it to their .gitignore.The signature of Lake.buildO has changed, args has been split into weakArgs and traceArgs. traceArgs are included in the input trace and weakArgs are not. See Lake's FFI example for a demonstration of how to adapt to this change.
The signatures of Lean.importModules, Lean.Elab.headerToImports, and Lean.Elab.parseImports have changed from taking List Import to Array Import.
There is now an occs field in the configuration object for the rewrite tactic, allowing control of which occurrences of a pattern should be rewritten. This was previously a separate argument for Lean.MVarId.rewrite, and this has been removed in favour of an additional field of Rewrite.Config. It was not previously accessible from user tactics.
Lean.Meta.getConst? has been renamed. We have renamed getConst? to getUnfoldableConst? (and getConstNoEx? to getUnfoldableConstNoEx?). These were not intended to be part of the public API, but downstream projects had been using them (sometimes expecting different behaviour) incorrectly instead of Lean.getConstInfo.
dsimp / simp / simp_all now fail by default if they make no progress.
This can be overridden with the (config := { failIfUnchanged := false }) option. This change was made to ease manual use of simp (with complicated goals it can be hard to tell if it was effective) and to allow easier flow control in tactics internally using simp. See the summary discussion on zulip for more details.
simp_all now preserves order of hypotheses.
In order to support the failIfUnchanged configuration option for dsimp / simp / simp_all the way simp_all replaces hypotheses has changed. In particular it is now more likely to preserve the order of hypotheses. See simp_all reorders hypotheses unnecessarily. (Previously all non-dependent propositional hypotheses were reverted and reintroduced. Now only such hypotheses which were changed, or which come after a changed hypothesis, are reverted and reintroduced. This has the effect of preserving the ordering amongst the non-dependent propositional hypotheses, but now any dependent or non-propositional hypotheses retain their position amongst the unchanged non-dependent propositional hypotheses.) This may affect proofs that use rename_i, case ... =>, or next ... =>.
this is now a regular identifier again that is implicitly introduced by anonymous have := for the remainder of the tactic block. It used to be a keyword that was visible in all scopes and led to unexpected behavior when explicitly used as a binder name.
Make calc require the sequence of relation/proof-s to have the same indentation, and add calc alternative syntax allowing underscores _ in the first relation.
The flexible indentation in calc was often used to align the relation symbols:
example (x y : Nat) : (x + y) * (x + y) = x * x + y * x + x * y + y * y := calc (x + y) * (x + y) = (x + y) * x + (x + y) * y := by rw [Nat.mul_add] -- improper indentation _ = x * x + y * x + (x + y) * y := by rw [Nat.add_mul] _ = x * x + y * x + (x * y + y * y) := by rw [Nat.add_mul] _ = x * x + y * x + x * y + y * y := by rw [←Nat.add_assoc]
This is no longer legal. The new syntax puts the first term right after the calc and each step has the same indentation:
example (x y : Nat) : (x + y) * (x + y) = x * x + y * x + x * y + y * y := calc (x + y) * (x + y) _ = (x + y) * x + (x + y) * y := by rw [Nat.mul_add] _ = x * x + y * x + (x + y) * y := by rw [Nat.add_mul] _ = x * x + y * x + (x * y + y * y) := by rw [Nat.add_mul] _ = x * x + y * x + x * y + y * y := by rw [←Nat.add_assoc]
Update Lake to latest prerelease.
Make go-to-definition on a typeclass projection application go to the instance(s).
Add linter.deprecated option to silence deprecation warnings.
simp can track information and can print an equivalent simp only. PR #1626.
Enforce uniform indentation in tactic blocks / do blocks. See issue #1606.
Moved AssocList, HashMap, HashSet, RBMap, RBSet, PersistentArray, PersistentHashMap, PersistentHashSet to the Lean package. The standard library contains versions that will evolve independently to simplify bootstrapping process.
Standard library moved to the std4 GitHub repository.
InteractiveGoals now has information that a client infoview can use to show what parts of the goal have changed after applying a tactic. PR #1610.
Add [inheritDoc] attribute. PR #1480.
Expose that panic = default. PR #1614.
New code generator project has started.
Remove description argument from register_simp_attr. PR #1566.
Many new doc strings have been added to declarations at Init.
Update Lake to v4.0.0. See the v4.0.0 release notes for detailed changes.
Mutual declarations in different namespaces are now supported. Example:
mutual def Foo.boo (x : Nat) := match x with | 0 => 1 | x + 1 => 2*Boo.bla x def Boo.bla (x : Nat) := match x with | 0 => 2 | x+1 => 3*Foo.boo x end
A namespace is automatically created for the common prefix. Example:
mutual def Tst.Foo.boo (x : Nat) := ... def Tst.Boo.bla (x : Nat) := ... end
expands to
namespace Tst mutual def Foo.boo (x : Nat) := ... def Boo.bla (x : Nat) := ... end end Tst
Allow users to install their own deriving handlers for existing type classes. See example at Simple.lean.
Add tactic congr (num)?. See doc string for additional details.
match-syntax notation now checks for unused alternatives. See issue #1371.
Auto-completion for structure instance fields. Example:
example : Nat × Nat := { f -- HERE }
fst now appears in the list of auto-completion suggestions.
Auto-completion for dotted identifier notation. Example:
example : Nat := .su -- HERE
succ now appears in the list of auto-completion suggestions.
nat_lit is not needed anymore when declaring OfNat instances. See issues #1389 and #875. Example:
inductive Bit where | zero | one instance inst0 : OfNat Bit 0 where ofNat := Bit.zero instance : OfNat Bit 1 where ofNat := Bit.one example : Bit := 0 example : Bit := 1
Add [elabAsElim] attribute (it is called elab_as_eliminator in Lean 3). Motivation: simplify the Mathlib port to Lean 4.
Trans type class now accepts relations in Type u. See this Zulip issue.
Accept unescaped keywords as inductive constructor names. Escaping can often be avoided at use sites via dot notation.
inductive MyExpr | let : ... def f : MyExpr → MyExpr | .let ... => .let ...
Throw an error message at parametric local instances such as [Nat -> Decidable p]. The type class resolution procedure cannot use this kind of local instance because the parameter does not have a forward dependency. This check can be disabled using set_option checkBinderAnnotations false.
Add option pp.showLetValues. When set to false, the info view hides the value of let-variables in a goal. By default, it is true when visualizing tactic goals, and false otherwise. See issue #1345 for additional details.
Add option warningAsError. When set to true, warning messages are treated as errors.
Support dotted notation and named arguments in patterns. Example:
def getForallBinderType (e : Expr) : Expr := match e with | .forallE (binderType := type) .. => type | _ => panic! "forall expected"
“jump-to-definition” now works for function names embedded in the following attributes @[implementedBy funName], @[tactic parserName], @[termElab parserName], @[commandElab parserName], @[builtinTactic parserName], @[builtinTermElab parserName], and @[builtinCommandElab parserName]. See issue #1350.
Improve MVarId methods discoverability. See issue #1346. We still have to add similar methods for FVarId, LVarId, Expr, and other objects. Many existing methods have been marked as deprecated.
Add attribute [deprecated] for marking deprecated declarations. Examples:
def g (x : Nat) := x + 1 -- Whenever `f` is used, a warning message is generated suggesting to use `g` instead. @[deprecated g] def f (x : Nat) := x + 1 #check f 0 -- warning: `f` has been deprecated, use `g` instead -- Whenever `h` is used, a warning message is generated. @[deprecated] def h (x : Nat) := x + 1 #check h 0 -- warning: `h` has been deprecated
Add type LevelMVarId (and abbreviation LMVarId) for universe level metavariable ids. Motivation: prevent meta-programmers from mixing up universe and expression metavariable ids.
Improve calc term and tactic. See issue #1342.
Relaxed antiquotation parsing further reduces the need for explicit $x:p antiquotation kind annotations.
Add support for computed fields in inductives. Example:
inductive Exp | var (i : Nat) | app (a b : Exp) with @[computedField] hash : Exp → Nat | .var i => i | .app a b => a.hash * b.hash + 1
The result of the Exp.hash function is then stored as an extra “computed” field in the .var and .app constructors; Exp.hash accesses this field and thus runs in constant time (even on dag-like values).
Update a[i] notation. It is now based on the typeclass
class GetElem (cont : Type u) (idx : Type v) (elem : outParam (Type w)) (dom : outParam (cont → idx → Prop)) where getElem (xs : cont) (i : idx) (h : dom xs i) : Elem
The notation a[i] is now defined as follows
macro:max x:term noWs "[" i:term "]" : term => `(getElem $x $i (by get_elem_tactic))
The proof that i is a valid index is synthesized using the tactic get_elem_tactic. For example, the type Array α has the following instances
instance : GetElem (Array α) Nat α fun xs i => LT.lt i xs.size where ... instance : GetElem (Array α) USize α fun xs i => LT.lt i.toNat xs.size where ...
You can use the notation a[i]'h to provide the proof manually. Two other notations were introduced: a[i]! and a[i]?, For a[i]!, a panic error message is produced at runtime if i is not a valid index. a[i]? has type Option α, and a[i]? evaluates to none if the index i is not valid. The three new notations are defined as follows:
@[inline] def getElem' [GetElem cont idx elem dom] (xs : cont) (i : idx) (h : dom xs i) : elem := getElem xs i h @[inline] def getElem! [GetElem cont idx elem dom] [Inhabited elem] (xs : cont) (i : idx) [Decidable (dom xs i)] : elem := if h : _ then getElem xs i h else panic! "index out of bounds" @[inline] def getElem? [GetElem cont idx elem dom] (xs : cont) (i : idx) [Decidable (dom xs i)] : Option elem := if h : _ then some (getElem xs i h) else none macro:max x:term noWs "[" i:term "]" noWs "?" : term => `(getElem? $x $i) macro:max x:term noWs "[" i:term "]" noWs "!" : term => `(getElem! $x $i) macro x:term noWs "[" i:term "]'" h:term:max : term => `(getElem' $x $i $h)
See discussion on Zulip. Examples:
example (a : Array Int) (i : Nat) : Int := a[i] -- Error: failed to prove index is valid ... example (a : Array Int) (i : Nat) (h : i < a.size) : Int := a[i] -- Ok example (a : Array Int) (i : Nat) : Int := a[i]! -- Ok example (a : Array Int) (i : Nat) : Option Int := a[i]? -- Ok example (a : Array Int) (h : a.size = 2) : Int := a[0]'(by rw [h]; decide) -- Ok example (a : Array Int) (h : a.size = 2) : Int := have : 0 < a.size := by rw [h]; decide have : 1 < a.size := by rw [h]; decide a[0] + a[1] -- Ok example (a : Array Int) (i : USize) (h : i.toNat < a.size) : Int := a[i] -- Ok
The get_elem_tactic is defined as
macro "get_elem_tactic" : tactic => `(first | get_elem_tactic_trivial | fail "failed to prove index is valid, ..." )
The get_elem_tactic_trivial auxiliary tactic can be extended using macro_rules. By default, it tries trivial, simp_arith, and a special case for Fin. In the future, it will also try linarith. You can extend get_elem_tactic_trivial using my_tactic as follows
macro_rules | `(tactic| get_elem_tactic_trivial) => `(tactic| my_tactic)
Note that Idx's type in GetElem does not depend on Cont. So, you cannot write the instance instance : GetElem (Array α) (Fin ??) α fun xs i => ..., but the Lean library comes equipped with the following auxiliary instance:
instance [GetElem cont Nat elem dom] : GetElem cont (Fin n) elem fun xs i => dom xs i where getElem xs i h := getElem xs i.1 h
and helper tactic
macro_rules | `(tactic| get_elem_tactic_trivial) => `(tactic| apply Fin.val_lt_of_le; get_elem_tactic_trivial; done)
Example:
example (a : Array Nat) (i : Fin a.size) := a[i] -- Ok example (a : Array Nat) (h : n ≤ a.size) (i : Fin n) := a[i] -- Ok
Better support for qualified names in recursive declarations. The following is now supported:
namespace Nat def fact : Nat → Nat | 0 => 1 | n+1 => (n+1) * Nat.fact n end Nat
Add support for CommandElabM monad at #eval. Example:
import Lean open Lean Elab Command #eval do let id := mkIdent `foo elabCommand (← `(def $id := 10)) #eval foo -- 10
Try to elaborate do notation even if the expected type is not available. We still delay elaboration when the expected type is not available. This change is particularly useful when writing examples such as
#eval do IO.println "hello" IO.println "world"
That is, we don't have to use the idiom #eval show IO _ from do ... anymore. Note that auto monadic lifting is less effective when the expected type is not available. Monadic polymorphic functions (e.g., ST.Ref.get) also require the expected type.
On Linux, panics now print a backtrace by default, which can be disabled by setting the environment variable LEAN_BACKTRACE to 0. Other platforms are TBD.
The group(·) syntax combinator is now introduced automatically where necessary, such as when using multiple parsers inside (...)+.
Add “Typed Macros”: syntax trees produced and accepted by syntax antiquotations now remember their syntax kinds, preventing accidental production of ill-formed syntax trees and reducing the need for explicit :kind antiquotation annotations. See PR for details.
Aliases of protected definitions are protected too. Example:
protected def Nat.double (x : Nat) := 2*x namespace Ex export Nat (double) -- Add alias Ex.double for Nat.double end Ex open Ex #check Ex.double -- Ok #check double -- Error, `Ex.double` is alias for `Nat.double` which is protected
Use IO.getRandomBytes to initialize random seed for IO.rand. See discussion at this PR.
Improve dot notation and aliases interaction. See discussion on Zulip for additional details. Example:
def Set (α : Type) := α → Prop def Set.union (s₁ s₂ : Set α) : Set α := fun a => s₁ a ∨ s₂ a def FinSet (n : Nat) := Fin n → Prop namespace FinSet export Set (union) -- FinSet.union is now an alias for `Set.union` end FinSet example (x y : FinSet 10) : FinSet 10 := x.union y -- Works
ext and enter conv tactics can now go inside let-declarations. Example:
example (g : Nat → Nat) (y : Nat) (h : let x := y + 1; g (0+x) = x) : g (y + 1) = y + 1 := by conv at h => enter [x, 1, 1]; rw [Nat.zero_add] /- g : Nat → Nat y : Nat h : let x := y + 1; g x = x ⊢ g (y + 1) = y + 1 -/ exact h
Add zeta conv tactic to expand let-declarations. Example:
example (h : let x := y + 1; 0 + x = y) : False := by conv at h => zeta; rw [Nat.zero_add] /- y : Nat h : y + 1 = y ⊢ False -/ simp_arith at h
Improve namespace resolution. See issue #1224. Example:
import Lean open Lean Parser Elab open Tactic -- now opens both `Lean.Parser.Tactic` and `Lean.Elab.Tactic`
Rename constant command to opaque. See discussion at Zulip.
Extend induction and cases syntax: multiple left-hand-sides in a single alternative. This extension is very similar to the one implemented for match expressions. Examples:
inductive Foo where | mk1 (x : Nat) | mk2 (x : Nat) | mk3 def f (v : Foo) := match v with | .mk1 x => x + 1 | .mk2 x => 2*x + 1 | .mk3 => 1 theorem f_gt_zero : f v > 0 := by cases v with | mk1 x | mk2 x => simp_arith! -- New feature used here! | mk3 => decide
Add unnamed antiquotation $_ for use in syntax quotation patterns.
Add unused variables linter. Feedback welcome!
Lean now generates an error if the body of a declaration body contains a universe parameter that does not occur in the declaration type, nor is an explicit parameter. Examples:
/- The following declaration now produces an error because `PUnit` is universe polymorphic, but the universe parameter does not occur in the function type `Nat → Nat` -/ def f (n : Nat) : Nat := let aux (_ : PUnit) : Nat := n + 1 aux ⟨⟩ /- The following declaration is accepted because the universe parameter was explicitly provided in the function signature. -/ def g.{u} (n : Nat) : Nat := let aux (_ : PUnit.{u}) : Nat := n + 1 aux ⟨⟩
Add subst_vars tactic.
Fix autoParam in structure fields lost in multiple inheritance..
Add [eliminator] attribute. It allows users to specify default recursor/eliminators for the induction and cases tactics. It is an alternative for the using notation. Example:
@[eliminator] protected def recDiag {motive : Nat → Nat → Sort u} (zero_zero : motive 0 0) (succ_zero : (x : Nat) → motive x 0 → motive (x + 1) 0) (zero_succ : (y : Nat) → motive 0 y → motive 0 (y + 1)) (succ_succ : (x y : Nat) → motive x y → motive (x + 1) (y + 1)) (x y : Nat) : motive x y := let rec go : (x y : Nat) → motive x y | 0, 0 => zero_zero | x+1, 0 => succ_zero x (go x 0) | 0, y+1 => zero_succ y (go 0 y) | x+1, y+1 => succ_succ x y (go x y) go x y termination_by go x y => (x, y) def f (x y : Nat) := match x, y with | 0, 0 => 1 | x+1, 0 => f x 0 | 0, y+1 => f 0 y | x+1, y+1 => f x y termination_by f x y => (x, y) example (x y : Nat) : f x y > 0 := by induction x, y <;> simp [f, *]
Add support for casesOn applications to structural and well-founded recursion modules. This feature is useful when writing definitions using tactics. Example:
inductive Foo where | a | b | c | pair: Foo × Foo → Foo def Foo.deq (a b : Foo) : Decidable (a = b) := by cases a <;> cases b any_goals apply isFalse Foo.noConfusion any_goals apply isTrue rfl case pair a b => let (a₁, a₂) := a let (b₁, b₂) := b exact match deq a₁ b₁, deq a₂ b₂ with | isTrue h₁, isTrue h₂ => isTrue (by rw [h₁,h₂]) | isFalse h₁, _ => isFalse (fun h => by cases h; cases (h₁ rfl)) | _, isFalse h₂ => isFalse (fun h => by cases h; cases (h₂ rfl))
Option is again a monad. The auxiliary type OptionM has been removed. See Zulip thread.
Improve split tactic. It used to fail on match expressions of the form match h : e with ... where e is not a free variable. The failure used to occur during generalization.
New encoding for match-expressions that use the h : notation for discriminants. The information is not lost during delaboration, and it is the foundation for a better split tactic. at delaboration time. Example:
#print Nat.decEq /- protected def Nat.decEq : (n m : Nat) → Decidable (n = m) := fun n m => match h : Nat.beq n m with | true => isTrue (_ : n = m) | false => isFalse (_ : ¬n = m) -/
exists tactic is now takes a comma separated list of terms.
Add dsimp and dsimp! tactics. They guarantee the result term is definitionally equal, and only apply rfl-theorems.
Fix binder information for match patterns that use definitions tagged with [matchPattern] (e.g., Nat.add). We now have proper binder information for the variable y in the following example.
def f (x : Nat) : Nat := match x with | 0 => 1 | y + 1 => y
(Fix) the default value for structure fields may now depend on the structure parameters. Example:
structure Something (i: Nat) where n1: Nat := 1 n2: Nat := 1 + i def s : Something 10 := {} example : s.n2 = 11 := rfl
Apply rfl theorems at the dsimp auxiliary method used by simp. dsimp can be used anywhere in an expression because it preserves definitional equality.
Refine auto bound implicit feature. It does not consider anymore unbound variables that have the same name of a declaration being defined. Example:
def f : f → Bool := -- Error at second `f` fun _ => true inductive Foo : List Foo → Type -- Error at second `Foo` | x : Foo []
Before this refinement, the declarations above would be accepted and the second f and Foo would be treated as auto implicit variables. That is, f : {f : Sort u} → f → Bool, and Foo : {Foo : Type u} → List Foo → Type.
Fix syntax highlighting for recursive declarations. Example
inductive List (α : Type u) where | nil : List α -- `List` is not highlighted as a variable anymore | cons (head : α) (tail : List α) : List α def List.map (f : α → β) : List α → List β | [] => [] | a::as => f a :: map f as -- `map` is not highlighted as a variable anymore
Add autoUnfold option to Lean.Meta.Simp.Config, and the following macros
simp! for simp (config := { autoUnfold := true })simp_arith! for simp (config := { autoUnfold := true, arith := true })simp_all! for simp_all (config := { autoUnfold := true })simp_all_arith! for simp_all (config := { autoUnfold := true, arith := true })When the autoUnfold is set to true, simp tries to unfold the following kinds of definition
match-expression. This kind of definition is only unfolded if the match can be reduced. Example:def append (as bs : List α) : List α := match as with | [] => bs | a :: as => a :: append as bs theorem append_nil (as : List α) : append as [] = as := by induction as <;> simp_all! theorem append_assoc (as bs cs : List α) : append (append as bs) cs = append as (append bs cs) := by induction as <;> simp_all!
Add save tactic for creating checkpoints more conveniently. Example:
example : <some-proposition> := by tac_1 tac_2 save tac_3 ...
is equivalent to
example : <some-proposition> := by checkpoint tac_1 tac_2 tac_3 ...
Remove support for {} annotation from inductive datatype constructors. This annotation was barely used, and we can control the binder information for parameter bindings using the new inductive family indices to parameter promotion. Example: the following declaration using {}
inductive LE' (n : Nat) : Nat → Prop where | refl {} : LE' n n -- Want `n` to be explicit | succ : LE' n m → LE' n (m+1)
can now be written as
inductive LE' : Nat → Nat → Prop where | refl (n : Nat) : LE' n n | succ : LE' n m → LE' n (m+1)
In both cases, the inductive family has one parameter and one index. Recall that the actual number of parameters can be retrieved using the command #print.
Remove support for {} annotation in the structure command.
Several improvements to LSP server. Examples: “jump to definition” in mutually recursive sections, fixed incorrect hover information in “match”-expression patterns, “jump to definition” for pattern variables, fixed auto-completion in function headers, etc.
In macro ... xs:p* ... and similar macro bindings of combinators, xs now has the correct type Array Syntax
Identifiers in syntax patterns now ignore macro scopes during matching.
Improve binder names for constructor auto implicit parameters. Example, given the inductive datatype
inductive Member : α → List α → Type u | head : Member a (a::as) | tail : Member a bs → Member a (b::bs)
before:
#check @Member.head -- @Member.head : {x : Type u_1} → {a : x} → {as : List x} → Member a (a :: as)
now:
#check @Member.head -- @Member.head : {α : Type u_1} → {a : α} → {as : List α} → Member a (a :: as)
Improve error message when constructor parameter universe level is too big.
Add support for for h : i in [start:stop] do .. where h : i ∈ [start:stop]. This feature is useful for proving termination of functions such as:
inductive Expr where | app (f : String) (args : Array Expr) def Expr.size (e : Expr) : Nat := Id.run do match e with | app f args => let mut sz := 1 for h : i in [: args.size] do -- h.upper : i < args.size sz := sz + size (args.get ⟨i, h.upper⟩) return sz
Add tactic case'. It is similar to case, but does not admit the goal on failure. For example, the new tactic is useful when writing tactic scripts where we need to use case' at first | ... | ..., and we want to take the next alternative when case' fails.
Add tactic macro
macro "stop" s:tacticSeq : tactic => `(repeat sorry)
See discussion on Zulip.
When displaying goals, we do not display inaccessible proposition names if they do not have forward dependencies. We still display their types. For example, the goal
case node.inl.node β : Type u_1 b : BinTree β k : Nat v : β left : Tree β key : Nat value : β right : Tree β ihl : BST left → Tree.find? (Tree.insert left k v) k = some v ihr : BST right → Tree.find? (Tree.insert right k v) k = some v h✝ : k < key a✝³ : BST left a✝² : ForallTree (fun k v => k < key) left a✝¹ : BST right a✝ : ForallTree (fun k v => key < k) right ⊢ BST left
is now displayed as
case node.inl.node β : Type u_1 b : BinTree β k : Nat v : β left : Tree β key : Nat value : β right : Tree β ihl : BST left → Tree.find? (Tree.insert left k v) k = some v ihr : BST right → Tree.find? (Tree.insert right k v) k = some v : k < key : BST left : ForallTree (fun k v => k < key) left : BST right : ForallTree (fun k v => key < k) right ⊢ BST left
The hypothesis name is now optional in the by_cases tactic.
Fix inconsistency between syntax and kind names. The node kinds numLit, charLit, nameLit, strLit, and scientificLit are now called num, char, name, str, and scientific respectively. Example: we now write
macro_rules | `($n:num) => `("hello")
instead of
macro_rules | `($n:numLit) => `("hello")
(Experimental) New checkpoint <tactic-seq> tactic for big interactive proofs.
Rename tactic nativeDecide => native_decide.
Antiquotations are now accepted in any syntax. The incQuotDepth syntax parser is therefore obsolete and has been removed.
Renamed tactic nativeDecide => native_decide.
“Cleanup” local context before elaborating a match alternative right-hand-side. Examples:
example (x : Nat) : Nat := match g x with | (a, b) => _ -- Local context does not contain the auxiliary `_discr := g x` anymore example (x : Nat × Nat) (h : x.1 > 0) : f x > 0 := by match x with | (a, b) => _ -- Local context does not contain the `h✝ : x.fst > 0` anymore
Improve let-pattern (and have-pattern) macro expansion. In the following example,
example (x : Nat × Nat) : f x > 0 := by let (a, b) := x done
The resulting goal is now ... |- f (a, b) > 0 instead of ... |- f x > 0.
Add cross-compiled aarch64 Linux and aarch64 macOS releases.
Add tutorial-like examples to our documentation, rendered using LeanInk+Alectryon.
simp now takes user-defined simp-attributes. You can define a new simp attribute by creating a file (e.g., MySimp.lean) containing
import Lean open Lean.Meta initialize my_ext : SimpExtension ← registerSimpAttr `my_simp "my own simp attribute"
If you don't need to access my_ext, you can also use the macro
import Lean register_simp_attr my_simp "my own simp attribute"
Recall that the new simp attribute is not active in the Lean file where it was defined. Here is a small example using the new feature.
import MySimp def f (x : Nat) := x + 2 def g (x : Nat) := x + 1 @[my_simp] theorem f_eq : f x = x + 2 := rfl @[my_simp] theorem g_eq : g x = x + 1 := rfl example : f x + g x = 2*x + 3 := by simp_arith [my_simp]
Extend match syntax: multiple left-hand-sides in a single alternative. Example:
def fib : Nat → Nat | 0 | 1 => 1 | n+2 => fib n + fib (n+1)
This feature was discussed at issue 371. It was implemented as a macro expansion. Thus, the following is accepted.
inductive StrOrNum where | S (s : String) | I (i : Int) def StrOrNum.asString (x : StrOrNum) := match x with | I a | S a => toString a
Improve #eval command. Now, when it fails to synthesize a Lean.MetaEval instance for the result type, it reduces the type and tries again. The following example now works without additional annotations
def Foo := List Nat def test (x : Nat) : Foo := [x, x+1, x+2] #eval test 4
rw tactic can now apply auto-generated equation theorems for a given definition. Example:
example (a : Nat) (h : n = 1) : [a].length = n := by rw [List.length] trace_state -- .. |- [].length + 1 = n rw [List.length] trace_state -- .. |- 0 + 1 = n rw [h]
Extend dot-notation x.field for arrow types. If type of x is an arrow, we look up for Function.field. For example, given f : Nat → Nat and g : Nat → Nat, f.comp g is now notation for Function.comp f g.
The new .<identifier> notation is now also accepted where a function type is expected.
example (xs : List Nat) : List Nat := .map .succ xs example (xs : List α) : Std.RBTree α ord := xs.foldl .insert ∅
Support notation let <pattern> := <expr> | <else-case> in do blocks.
Remove support for “auto” pure. In the Zulip thread, the consensus seemed to be that “auto” pure is more confusing than it's worth.
Remove restriction in congr theorems that all function arguments on the left-hand-side must be free variables. For example, the following theorem is now a valid congr theorem.
@[congr] theorem dep_congr [DecidableEq ι] {p : ι → Set α} [∀ i, Inhabited (p i)] : ∀ {i j} (h : i = j) (x : p i) (y : α) (hx : x = y), Pi.single (f := (p ·)) i x = Pi.single (f := (p ·)) j ⟨y, hx ▸ h ▸ x.2⟩ :=
Improve elaboration postponement heuristic when expected type is a metavariable. Lean now reduces the expected type before performing the test.
Remove deprecated leanpkg in favor of Lake now bundled with Lean.
Various improvements to go-to-definition & find-all-references accuracy.
Auto generated congruence lemmas with support for casts on proofs and Decidable instances (see wishlist).
Rename option autoBoundImplicitLocal => autoImplicit.
Relax auto-implicit restrictions. The command set_option relaxedAutoImplicit false disables the relaxations.
contradiction tactic now closes the goal if there is a False.elim application in the target.
Renamed tatic byCases => by_cases (motivation: enforcing naming convention).
Local instances occurring in patterns are now considered by the type class resolution procedure. Example:
def concat : List ((α : Type) × ToString α × α) → String | [] => "" | ⟨_, _, a⟩ :: as => toString a ++ concat as
Notation for providing the motive for match expressions has changed. before:
match x, rfl : (y : Nat) → x = y → Nat with | 0, h => ... | x+1, h => ...
now:
match (motive := (y : Nat) → x = y → Nat) x, rfl with | 0, h => ... | x+1, h => ...
With this change, the notation for giving names to equality proofs in match-expressions is not whitespace sensitive anymore. That is, we can now write
match h : sort.swap a b with | (r₁, r₂) => ... -- `h : sort.swap a b = (r₁, r₂)`
(generalizing := true) is the default behavior for match expressions even if the expected type is not a proposition. In the following example, we used to have to include (generalizing := true) manually.
inductive Fam : Type → Type 1 where | any : Fam α | nat : Nat → Fam Nat example (a : α) (x : Fam α) : α := match x with | Fam.any => a | Fam.nat n => n
We now use PSum (instead of Sum) when compiling mutually recursive definitions using well-founded recursion.
Better support for parametric well-founded relations. See issue #1017. This change affects the low-level termination_by' hint because the fixed prefix of the function parameters in not “packed” anymore when constructing the well-founded relation type. For example, in the following definition, as is part of the fixed prefix, and is not packed anymore. In previous versions, the termination_by' term would be written as measure fun ⟨as, i, _⟩ => as.size - i
def sum (as : Array Nat) (i : Nat) (s : Nat) : Nat := if h : i < as.size then sum as (i+1) (s + as.get ⟨i, h⟩) else s termination_by' measure fun ⟨i, _⟩ => as.size - i
Add while <cond> do <do-block>, repeat <do-block>, and repeat <do-block> until <cond> macros for do-block. These macros are based on partial definitions, and consequently are useful only for writing programs we don't want to prove anything about.
Add arith option to Simp.Config, the macro simp_arith expands to simp (config := { arith := true }). Only Nat and linear arithmetic is currently supported. Example:
example : 0 < 1 + x ∧ x + y + 2 ≥ y + 1 := by simp_arith
Add fail <string>? tactic that always fail.
Add support for acyclicity at dependent elimination. See issue #1022.
Add trace <string> tactic for debugging purposes.
Add nontrivial SizeOf instance for types Unit → α, and add support for them in the auto-generated SizeOf instances for user-defined inductive types. For example, given the inductive datatype
inductive LazyList (α : Type u) where | nil : LazyList α | cons (hd : α) (tl : LazyList α) : LazyList α | delayed (t : Thunk (LazyList α)) : LazyList α
we now have sizeOf (LazyList.delayed t) = 1 + sizeOf t instead of sizeOf (LazyList.delayed t) = 2.
Add support for guessing (very) simple well-founded relations when proving termination. For example, the following function does not require a termination_by annotation anymore.
def Array.insertAtAux (i : Nat) (as : Array α) (j : Nat) : Array α := if h : i < j then let as := as.swap! (j-1) j; insertAtAux i as (j-1) else as
Add support for for h : x in xs do ... notation where h : x ∈ xs. This is mainly useful for showing termination.
Auto implicit behavior changed for inductive families. An auto implicit argument occurring in inductive family index is also treated as an index (IF it is not fixed, see next item). For example
inductive HasType : Index n → Vector Ty n → Ty → Type where
is now interpreted as
inductive HasType : {n : Nat} → Index n → Vector Ty n → Ty → Type where
To make the previous feature more convenient to use, we promote a fixed prefix of inductive family indices to parameters. For example, the following declaration is now accepted by Lean
inductive Lst : Type u → Type u | nil : Lst α | cons : α → Lst α → Lst α
and α in Lst α is a parameter. The actual number of parameters can be inspected using the command #print Lst. This feature also makes sure we still accept the declaration
inductive Sublist : List α → List α → Prop | slnil : Sublist [] [] | cons l₁ l₂ a : Sublist l₁ l₂ → Sublist l₁ (a :: l₂) | cons2 l₁ l₂ a : Sublist l₁ l₂ → Sublist (a :: l₁) (a :: l₂)
Added auto implicit “chaining”. Unassigned metavariables occurring in the auto implicit types now become new auto implicit locals. Consider the following example:
inductive HasType : Fin n → Vector Ty n → Ty → Type where | stop : HasType 0 (ty :: ctx) ty | pop : HasType k ctx ty → HasType k.succ (u :: ctx) ty
ctx is an auto implicit local in the two constructors, and it has type ctx : Vector Ty ?m. Without auto implicit “chaining”, the metavariable ?m will remain unassigned. The new feature creates yet another implicit local n : Nat and assigns n to ?m. So, the declaration above is shorthand for
inductive HasType : {n : Nat} → Fin n → Vector Ty n → Ty → Type where | stop : {ty : Ty} → {n : Nat} → {ctx : Vector Ty n} → HasType 0 (ty :: ctx) ty | pop : {n : Nat} → {k : Fin n} → {ctx : Vector Ty n} → {ty : Ty} → HasType k ctx ty → HasType k.succ (u :: ctx) ty
Eliminate auxiliary type annotations (e.g, autoParam and optParam) from recursor minor premises and projection declarations. Consider the following example
structure A := x : Nat h : x = 1 := by trivial example (a : A) : a.x = 1 := by have aux := a.h -- `aux` has now type `a.x = 1` instead of `autoParam (a.x = 1) auto✝` exact aux example (a : A) : a.x = 1 := by cases a with | mk x h => -- `h` has now type `x = 1` instead of `autoParam (x = 1) auto✝` assumption
We now accept overloaded notation in patterns, but we require the set of pattern variables in each alternative to be the same. Example:
inductive Vector (α : Type u) : Nat → Type u | nil : Vector α 0 | cons : α → Vector α n → Vector α (n+1) infix:67 " :: " => Vector.cons -- Overloading the `::` notation def head1 (x : List α) (h : x ≠ []) : α := match x with | a :: as => a -- `::` is `List.cons` here def head2 (x : Vector α (n+1)) : α := match x with | a :: as => a -- `::` is `Vector.cons` here
New notation .<identifier> based on Swift. The namespace is inferred from the expected type. See issue #944. Examples:
def f (x : Nat) : Except String Nat := if x > 0 then .ok x else .error "x is zero" namespace Lean.Elab open Lsp def identOf : Info → Option (RefIdent × Bool) | .ofTermInfo ti => match ti.expr with | .const n .. => some (.const n, ti.isBinder) | .fvar id .. => some (.fvar id, ti.isBinder) | _ => none | .ofFieldInfo fi => some (.const fi.projName, false) | _ => none def isImplicit (bi : BinderInfo) : Bool := bi matches .implicit end Lean.Elab