TODO.md
author wenzelm
Mon, 21 Jun 2021 22:08:01 +0200
changeset 60316 63cecf440235
parent 60315 352f02b89e67
child 60331 40eb8aa2b0d6
permissions -rw-r--r--
updated TODO;
wenzelm@60234
     1
* MW: check uses of Unsynchronized.ref vs. Synchronized.var;
wenzelm@60234
     2
wenzelm@60216
     3
* MW: clarify/eliminate Isabelle/Scala add-ons (presently unused)
wenzelm@60216
     4
wenzelm@60216
     5
    diff -r /home/makarius/isabelle/repos-Isabelle2021/src/Pure/build-jars ./src/Pure/build-jars
wenzelm@60216
     6
    11a12
wenzelm@60216
     7
    >   src/Tools/isac/BridgeJEdit/isac.scala
wenzelm@60216
     8
wenzelm@60216
     9
    diff -r /home/makarius/isabelle/repos-Isabelle2021/src/Pure/Tools/scala_project.scala ./src/Pure/Tools/scala_project.scala
wenzelm@60216
    10
    76a77
wenzelm@60216
    11
    >       "src/Tools/isac/etc" -> Path.explode("isabelle.isac"),
wenzelm@60225
    12
wenzelm@60281
    13
wenzelm@60316
    14
* Eliminate Thy_Info.get_theory eventually: should take theory from ancestory
wenzelm@60316
    15
  within current context.
wenzelm@60316
    16
wenzelm@60295
    17
* Clarify symmetric rule: Thm.apply_attribute Calculation.symmetric thm context (!?);
wenzelm@60295
    18
wenzelm@60316
    19
* KEStore_Elems: Should we eliminate union_overwrite and use standard namespace merge?
wenzelm@60316
    20
  (Exception: rlss with its special cross-theory merge.)
wenzelm@60285
    21
wenzelm@60281
    22
* What is the purpose of "#numeral" instead of plain numeral?
wenzelm@60281
    23
wenzelm@60281
    24
* Check/clarify Context.theory_name vs. Context.theory_long_name.
wenzelm@60281
    25
wenzelm@60292
    26
* Eliminate mutable Rewrite_Ord.rew_ord' (!?);
wenzelm@60292
    27
wenzelm@60315
    28
* What is the idea behind KEStore_Elems.add_thes? How to do it properly in current Isabelle?
wenzelm@60315
    29
wenzelm@60315
    30
wenzelm@60315
    31
* WN: clarify add_calcs with non-existant constant "Integrate.add_new_c";
wenzelm@60229
    32
wenzelm@60311
    33
* WN: proper ML antiquotations for "Tactical.Try" etc. --- be careful about unclear situations,
wenzelm@60311
    34
  e.g. "Tactical.Try" vs. "Lucas_Interpreter.Try";
wenzelm@60311
    35
wenzelm@60304
    36
* WN: eliminate ThmC.numerals_to_Free, use existing Isabelle/HOL representation
wenzelm@60304
    37
    - clarify role of type "real" vs. "float" (see theory "HOL-Library.Float");
wenzelm@60302
    38
wenzelm@60311
    39
* WN: proper formal context with theory HOL-Library.Float, proper antiquotation @{const_name Float};
wenzelm@60316
    40
  (e.g. theory ISAC_Base imports "HOL-Library.Floar" instead of HOL.Complex_Main);
wenzelm@60311
    41
wenzelm@60301
    42
* WN: clarify Rule.Thm ("minus_divide_left", ...): Should this be @{rule_thm_sym} antiquotation?
wenzelm@60301
    43
wenzelm@60304
    44
* WN: check remaining MethodC.prep_input that use a different theory (e.g. "Diff"):
wenzelm@60304
    45
  Is this really required, or can we just use the 'method' command?
wenzelm@60304
    46
wenzelm@60311
    47
* WN: trim-down MethodC.prep_input and Problem.prep_input to what is really needed;
wenzelm@60311
    48
  improve errors via parse_term_strict;
wenzelm@60287
    49
wenzelm@60304
    50
* WN: eliminate global flags like "trace_on", replace Unsynchronized.ref by
wenzelm@60304
    51
wenzelm@60304
    52
    ML \<open>val rewrite_trace = Attrib.setup_config_bool \<^binding>\<open>rewrite_trace\<close> (K false);\<close>
wenzelm@60304
    53
wenzelm@60304
    54
* WN: Avoid Thm.get_name_hint --- somewhat fragile.
wenzelm@60304
    55
wenzelm@60284
    56
* WN: eliminate ThyC.to_ctxt, use Proof_Context.init_global inline to make more
wenzelm@60284
    57
  clear where the normal Isabelle context-discipline is bypassed;
wenzelm@60284
    58
wenzelm@60241
    59
* WN: more direct logical foundations wrt. Isabelle/HOL, eliminate many axiomatizations
wenzelm@60241
    60
    - quite often "axiomatization ..." can be turned into "lemma ... by auto"
wenzelm@60241
    61
      without further ado;
wenzelm@60241
    62
    - sometimes this requires to use more specific types / type classes;
wenzelm@60241
    63
    - sometimes this requires to use proper definitional mechanisms (e.g. 'primrec', 'fun');
wenzelm@60241
    64
    - a few "hard" cases will remain, to be reconsidered eventually (e.g. differentiation);
wenzelm@60234
    65
wenzelm@60247
    66
* WN: "fun pr_ord" is not required if used with @{make_string}, @{print}, @{print tracing};