first steps to the expr/stmt unification
This commit is contained in:
parent
3897a8c44b
commit
2afadc5c9c
8 changed files with 159 additions and 92 deletions
10
todo.txt
10
todo.txt
|
|
@ -10,18 +10,16 @@ version 0.9.2
|
|||
- parser/grammar:
|
||||
* check that of branches can only receive even simpler expressions, don't
|
||||
allow 'of (var x = 23; nkIdent)'
|
||||
* allow (var x = 12; for i in ... ; x) construct
|
||||
* try except as an expression
|
||||
* document (var x = 12; for i in ... ; x) construct
|
||||
- make use of commonType relation in expressions
|
||||
- further expr/stmt unification:
|
||||
- nkIfStmt vs nkIfExpr
|
||||
- start with JS backend and support exprs everywhere
|
||||
- then enhance C backend
|
||||
- OR: do the temp stuff in transf
|
||||
- rewrite nkCaseExpr handling
|
||||
- try except as an expression
|
||||
|
||||
Bugs
|
||||
====
|
||||
|
||||
- new parser breaks docgen
|
||||
- docgen: sometimes effects are listed twice
|
||||
- 'result' is not properly cleaned for NRVO
|
||||
- instantiated generics are listed in error messages
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue