Skip to content

Latest commit

 

History

History
145 lines (111 loc) · 4.75 KB

TODOs.org

File metadata and controls

145 lines (111 loc) · 4.75 KB

“discount rule” example?

  • <2017-01-04 Wed>

docstrings on test functions.

  • <2016-12-29 Thu>

JSONSchema-based validation of expressions?

  • <2016-12-30 Fri>

Semantical Static Analysis?

  • <2016-12-30 Fri>

docstring-field for func-val, func-val-params.

  • <2016-12-29 Thu>

annots for func-val-params?

  • <2016-12-29 Thu> arities(if it is a function-param)…

Comments-fields on everywhere?

  • <2016-12-27 Tue> Every node should be able to have a comment.

__repr__-methods for every ExprNode.

  • <2017-01-11 Wed>

Update the README.

  • <2016-12-28 Wed>
    1. Separate contents by sections.

complex functional examples in json?

  • <2017-01-04 Wed>
    1. SEE: funcall_test.py
    2. SEE: funcall_compose_test.py
  • <2017-01-11 Wed> [5/5]
    1. [X] closure1-inc
    2. [X] closure2-counter
    3. [X] make-adder
      • Cancel. not a matter anymore
    4. [X] incx
    5. [X] compose1, inc1, square, and test-compose1

standalone interpreter.

  • <2017-01-04 Wed>

eval_json_str or eval_json_inputstream?

  • <2017-01-04 Wed>

JSON Ser/DeSer?

  • <2016-12-27 Tue>
  • <2017-01-02 Mon>
    • Just using json.JSONEncoder/JSONDecoder in standard library.
      • because Pyckson isn’t succinct for this.

eq, ne for func-literals? builtin-ops

  • <2016-12-28 Wed> almost everything!
    1. now it’s done for most literals. (except fun-val, because of its expr-node…)
    2. had to be done for json ser-deser.

Evaluatable type-hierarchy.

  • <2017-01-02 Mon>
    • Simplify typing signatures.

Q. ParamVals for MappedFunction?

  • <2016-12-30 Fri> with that, it would be more descriptive.

CaseItem, CondItem, FunctionParamVal .. is not a evaluatable-nodes.

  • <2016-12-30 Fri> Hence, change the type.
    • not with FunctionParamVal, these have own evaluator. (it is a expr.)

Apply Python typing signatures on funcs?

  • <2016-12-30 Fri>

Arrange packages (nodes, builtin-ops, evaluators)

  • <2016-12-28 Wed>

Rename Plus/Minus -> Add/Sub.

  • <2016-12-30 Fri>

No-wrap/unwrap mapped-funcs?

  • <2016-12-30 Fri>

Max-Stack-Depth as a script? (not a testcase)

  • <2016-12-30 Fri>

Fix the bug of `test_func_composition`.

  • <2016-12-29 Thu>

let-bindings?

  • <2016-12-28 Wed>
    1. support upvar, global, const?
    2. depend each binding, DAC-graph.
    3. ..is it should be in primitives? or just implement with mapped-func?

const?

  • <2016-12-27 Tue>
    1. should Binding support this?
    2. ..or just implement this with its evaluator?

mapped-vars and mapped-funcs.

  • <2016-12-28 Wed>

Byte-code compiler?

  • <2016-12-29 Thu>
    • ..do it in JVM instead of this.
    • because there’s no actual bytecode emitter in python3. (only `dis` available.)

simple evaluators per builtin-ops.

  • <2016-12-28 Wed>

a stack needs for funcall?

  • <2016-12-28 Wed>
    • <2016-12-29 Thu> no-need. interpreted within py-stack.

the evaluator.

  • <2016-12-27 Tue>
    • or just use term interpreter.
      • because using same term evaluator for a node and nodes is confusing.

storing function defs?

  • <2016-12-28 Wed>
    1. in binding?
    2. as an object-tree?

Add some __repr__ to nodes.

  • <2016-12-28 Wed> for debugging.

exchange / and // ops in READMEs.

  • <2016-12-28 Wed> Just like in Python.

__eq__ methods for some literal-nodes?

  • <2016-12-28 Wed>

remove doctest.

  • <2016-12-28 Wed> just use doctests as docstrings.

pytest for elpy-test-runner.