data61 PSL issues - Githubissues

data61 / PSL

Other

65 stars 9 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

SeLFiE: Do we really need to invent fresh names in syntactic sugars?

#117 yutakang closed 4 years ago
15
SeLFiE: Do we need to distinguish if a parameter is `Path` or `NonPath`?

#116 yutakang closed 4 years ago
3
Quick_SeLFiE: evaluation strategy

#115 yutakang closed 4 years ago
1
SeLFiE: clarify where I need to pass `term` to eval functions.

#114 yutakang closed 4 years ago
1
SeLFiE: Eval_Outer_Path.ML

#113 yutakang closed 4 years ago
1
SeLFiE: remove `And` and `Or` from some structures.

#112 yutakang closed 4 years ago
1
SeLFiE: Can we use the same qtyp for all structures?

#111 yutakang closed 4 years ago
1
SeLFiE: Do we really need two different evaluation functions for Inner and Outermost?

#110 yutakang closed 4 years ago
2
SeLFiE: Boolean operators have to take `Literal bool` in `From_Parameter_With_Bool_To_Bound.ML`

#109 yutakang closed 4 years ago
2
SeLFiE: can we not define `atomic_assert` in many signatures?

#108 yutakang closed 4 years ago
7
SeLFiE: Should I have only one `EVAL_PATH` instead of `EVAL_INNER_PATH` and `EVAL_OUTER_PATH`

#107 yutakang closed 5 years ago
5
SeLFiE: where to introduce new syntactic sugar for atomic assertions?

#106 yutakang closed 4 years ago
1
SeLFiE: syntax sugar for multi-argument function application and successive lambda-abstraction.

#105 yutakang closed 4 years ago
0
SeLFiE: bunched sugaring

#104 yutakang closed 4 years ago
1
SeLFiE: rename some signatures, structures, and files.

#103 yutakang closed 5 years ago
1
SeLFiE: should I pass around Proof.state inside the SeLFiE interpreter?

#102 yutakang closed 4 years ago
1
SeLFiE: develop a new construct `Is_Defined_With`

#101 yutakang closed 5 years ago
4
SeLFiE: remove Eval_Primitive

#100 yutakang closed 5 years ago
1
SeLFiE: Eval_Modifier should be introduced after Eval_Number and before Full_Path.

#99 yutakang closed 5 years ago
2
SeLFiE: merge Eval_Semantics and Eval_Syntax to produce Eval_SeLFiE.

#98 yutakang closed 4 years ago
6
SeLFiE: implement a light-weight type checker for the semantic part of SeLFiE.

#97 yutakang opened 5 years ago
1
SeLFiE: Should I introduce Full_Path between Eval_Semantics and Eval_Syntax?

#96 yutakang closed 5 years ago
3
SeLFiE: refactor Eval_Expression_Struct.ML

#95 yutakang closed 5 years ago
1
SeLFiE: swap the names of Eval_Syntax and Eval_Semantic.

#94 yutakang closed 5 years ago
1
SeLFiE: we should not have `Connective` in the `expr` in `Eval_Bound`.

#93 yutakang closed 5 years ago
5
SeLFiE: test Eval_Syntax

#92 yutakang closed 4 years ago
0
SeLFiE: implement a function to fetch relevant equations for the bootstrapping interpreter.

#91 yutakang closed 4 years ago
1
SeLFiE: change the type signature of eval in Eval_Syntax.

#90 yutakang closed 4 years ago
5
SeLFiE: `Some` as syntactic sugar?

#89 yutakang closed 5 years ago
1
SeLFiE: split the datatype `assertion` into two for bootstrapping.

#88 yutakang closed 4 years ago
2
LiFtEr: the `pred` field.

#87 yutakang opened 5 years ago
1
LiFtEr: Pattern and Isabelle keyword to define constants.

#86 yutakang closed 3 years ago
1
LiFtEr: detect the use of point-free style in the definition of a constant.

#85 yutakang opened 5 years ago
0
LiFtEr: New pattern "Pat_Comp" to check if pattern-matching is complete.

#84 yutakang closed 4 years ago
2
LiFtEr: Analyze the RHS of the definitions of the constants appearing in proof obligations.

#83 yutakang closed 5 years ago
3
PSL, PGT: Nunchaku with a short timeout.

#82 yutakang opened 5 years ago
0
LiFtEr: carefully limit the domain of Numb.

#81 yutakang closed 5 years ago
1
LiFtEr: assert_LiFtEr should take two strings in stead of two numbers.

#80 yutakang closed 5 years ago
1
LiFtEr: simultaneous induction with the and keyword for mutual recursion and nested recursion.

#79 yutakang closed 3 years ago
1
LiFtEr: All and Some should take any of trm, trm_occ, numb, or rule?

#78 yutakang closed 3 years ago
1
PSL, MeLoId, LiFtEr: replace `get_induct_rules` and `get_induct_rule_names` with `pstate_to_induct...`

#77 yutakang opened 5 years ago
1
LiFtEr: Use some functions from the function package to analyze the "pattern" of function definitions.

#76 yutakang opened 5 years ago
0
MiLkMaId/LiFtEr: Adding type annotations to some arguments of the `induct` method is sometimes useful.

#75 yutakang opened 5 years ago
0
LiFtEr: Remove `Trueprop`?

#74 yutakang closed 4 years ago
1
LiFtEr: Introduce a new language construct `Is_Rule_Of of (rule * subtrm_occ)`.

#73 yutakang closed 5 years ago
1
LiFtEr: Introduce a new language construct `Depth_Of`.

#72 yutakang closed 5 years ago
1
LiFtEr: Change 'All_Sub_Trm_Occ' and 'Some_Sub_Trm_Occ'

#71 yutakang closed 5 years ago
6
LiFtEr: separate core-syntax and syntax-sugars more clearly in `LiFtEr_Sig.ML` and `LiFtEr_Struct.ML`.

#70 yutakang closed 4 years ago
1
LiFtEr: paths in the original term?

#69 yutakang closed 4 years ago
1
LiFtEr: fix `is_nth_arg_of_induct_method` in `LiFtEr_Struct.ML`.

#68 yutakang closed 5 years ago
1

Previous Next