README: no enum literals, no switch yet
This commit is contained in:
parent
36361b3d13
commit
bf742f1699
1 changed files with 6 additions and 2 deletions
|
@ -24,10 +24,13 @@ negatively charged towards
|
|||
Be Properly Titled and i can't bother with that)
|
||||
|
||||
- function parameters must have a type always
|
||||
- ifs are always statements, not expressions (can't use if as an r-value)
|
||||
- no `++`, `--`
|
||||
(no `fn blah(x, y int)`, must be `fn blah(x int, y int)`)
|
||||
- ifs are always statements, not expressions
|
||||
(can't use if as an r-value: `x := if ...`)
|
||||
- no `++`, `--` (use `+=` and `-=`)
|
||||
- no `match`
|
||||
- no embedded structs
|
||||
- no enum literals (`x = .val2`)
|
||||
- no v orm
|
||||
- no codegen
|
||||
- no inline assembly
|
||||
|
@ -42,6 +45,7 @@ negatively charged towards
|
|||
- no generics yet
|
||||
- no attributes yet (`[live]`, `[skip]`)
|
||||
- no `defer` yet
|
||||
- no `switch` yet
|
||||
- no operator overloading methods yet
|
||||
- do we really want a type system (optionals included)
|
||||
- no error handling yet (`call() or {blah}`)
|
||||
|
|
Loading…
Reference in a new issue