Juraj Kirchheim

The trigger should be marked with `@:usedOnlyBy`.

Currently, things like `@:lazy @:prop` are possible. The `@:prop` just gets ignore, which is not the end of the world, but it should yield at least a warning.

Exprs.eval and stored typed expressions does not work for Haxe 4.3 +

2

See tests.

Probably will have to be a separate lib.

See https://github.com/haxetink/tink_unittest/issues/9#issuecomment-305165448

Consider SQL-ish syntax

6

For more SQL-like syntax (for those who prefer it): - `db.SELECT(_).FROM(User).WHERE(id == 42)` - `db.INSERT_INTO(User, [name, age]).VALUES(["Jack", 23], ["Joe", 35])` - `db.UPDATE(User).SET(age = age + 1).WHERE(birthDay == Date.now())` In particular...

Plain functions for conditions

1

Now that we have short lambdas in the language, I think this is a nice macro free way to write conditions: ```haxe db.User.where(u -> u.name == "JohnDoe"); ``` Also with...

I think we need to change `update` to be generated for every table. ```haxe var foobar = new Table(); $type(foobar.update);// { ?foo:Expr, ?bar:Expr } ``` For one I don't see...

Minimal example: ```haxe package ; function main() { var cfg:DialogConfig = { priority: 0, ui: (null:RenderResult), }; } @:forward abstract DialogConfig(DialogConfigData) from DialogConfigData { @:from static function fromRenderResult(r:RenderResult):DialogConfig return {...