1 * MW: check uses of Unsynchronized.ref vs. Synchronized.var;
3 * MW: clarify/eliminate Isabelle/Scala add-ons (presently unused)
5 diff -r /home/makarius/isabelle/repos-Isabelle2021/src/Pure/build-jars ./src/Pure/build-jars
7 > src/Tools/isac/BridgeJEdit/isac.scala
9 diff -r /home/makarius/isabelle/repos-Isabelle2021/src/Pure/Tools/scala_project.scala ./src/Pure/Tools/scala_project.scala
11 > "src/Tools/isac/etc" -> Path.explode("isabelle.isac"),
13 * Eliminate Thy_Info.get_theory eventually: should take theory from ancestory
14 within current context.
15 cf. e587c45cae0f note in Build_Thydata.thy
17 * Clarify symmetric rule: Thm.apply_attribute Calculation.symmetric thm context (!?);
20 * KEStore_Elems: Should we eliminate union_overwrite and use standard namespace merge?
21 (Exception: rlss with its special cross-theory merge.)
22 ? how adapt the different signatures ?
23 union_overwrite: ('a * 'a -> bool) -> 'a list -> 'a list -> 'a list
24 merge : ('a * 'a -> bool) -> 'a list * 'a list -> 'a list
26 * What is the purpose of "#numeral" instead of plain numeral?
29 * Check/clarify Context.theory_name vs. Context.theory_long_name.
30 present ISAC assumes 2 sessions in the MathEngine, Specify and Interpret,
31 and all Isac_Knowledge is in session Isac.
32 So Context.theory_name suffices
34 * Eliminate mutable Rewrite_Ord.rew_ord' (!?);
35 shall be done in connection with cf. e587c45cae0f note in Build_Thydata.thy
37 * What is the idea behind KEStore_Elems.add_thes? How to do it properly in current Isabelle?
38 https://static.miraheze.org/isacwiki/0/04/Isac-docu.pdf distinguishes
39 several kinds of ISAC users, in particular "math author (Mathematik-Autor)" and
40 "course designer (Kurs-Designer)". The latter just adds examples which re-use existing
41 knowledge designed by the former. KEStore_Elems.add_thes is an interface for the latter.
43 * WN: proper ML antiquotations for "Tactical.Try" etc. --- be careful about unclear situations,
44 e.g. "Tactical.Try" vs. "Lucas_Interpreter.Try";
46 * WN: Avoid Thm.get_name_hint and use Global_Theory.get_thm instead, get theory from References.T
47 and push theory through as argument of respective functions.
49 * WN: more direct logical foundations wrt. Isabelle/HOL, eliminate many axiomatizations
50 - quite often "axiomatization ..." can be turned into "lemma ... by auto"
52 - sometimes this requires to use more specific types / type classes;
53 - sometimes this requires to use proper definitional mechanisms (e.g. 'primrec', 'fun');
54 - a few "hard" cases will remain, to be reconsidered eventually (e.g. differentiation);
56 * WN: "fun pr_ord" is not required if used with @{make_string}, @{print}, @{print tracing};
57 takes only static arguments ----------------^^^^^^^^^^^^^^, not value of "hd_ord (f, g)"
58 ? are there better approximations to old output of (*1*) than with (*2*)
59 (*1*)val _ = tracing ("hd_ord (f, g) = " ^ ((pr_ord o hd_ord) (f, g)) );
60 (*2*)val _ = @{print tracing}{a = "hd_ord (f, g) = ", z = hd_ord (f, g)}(**)
63 * WN: eliminate global flags like "trace_on", replace Unsynchronized.ref by
66 val rewrite_trace = Attrib.setup_config_bool \<^binding>\<open>rewrite_trace\<close> (K false);
69 * WN: for calculation by use of Makarius' "problem" as boilerplate clarify:
70 - How inspect Token lists, e.g. from ML_Lex.read OR ML_Lex.read_source ?
71 - Why the ERROR in Demo_Example.thy at: \<open>problem pbl_bieg : "Biegelinien" = ..\<close> ?