Owlkettle 2.0.0 is a declarative GUI framwork for GTK 4

The `Property` widget in `custom_dialog.nim` is a simple viewable widget which is just an abstraction over the existing widgets. It is defined [here](https://github.com/can-lehmann/owlkettle/blob/main/examples/custom_dialog.nim#L29) and expands to a Box containing a Label. You should be able to

Owlkettle 2.0.0 is a declarative GUI framwork for GTK 4

Looks great! I really like that you could write something like Box: Label(@expand = false): text = "Hello" Run without breaking backwards compatibility. I will look into implementing something like this in Owlkettle.

Nim v1.6.6 support for Codewars

The issue with some of the tests I have seen is they use check() inside a procedure call which doesn't record a failure within Nim's unittest framework. So from the point of a user on codewars, all your tests look like they are passing even though they are clearly not suppose to. The check() isn

Nim v1.6.6 support for Codewars

Hey, yeah I did run a local test, and on my laptop I see like 6-9s to compile and run with -d:release. Yes there's a cache, so what I do is rm -rf./cac/*; time nim c -r -d:release --nimcache:cac tests.nim Run To detect compile flags I added when defined(

Nim v1.6.6 support for Codewars

hi - did you try running a test locally - it is fairly straight forward copying codewars_output.nim and one of the tests I was working on. It was very fast to compile, despite generating the 100 random tests. approx one second. I've tried release, arc, orc - all take 1 second to compile, but tak

Nim v1.6.6 support for Codewars

i created an issue: it seems like compile times are included, and template expansion of all the unittest stuff is taking too long. maybe using something other than unittest would be possible?