Andre von Houck

I think it's fine that Nim's ABI is largely undefined. Nim does not map well to plain C. I think my project [Genny](https://github.com/treeform/genny) solves this issue in a better way....

I think @beef331's library reinforces my point. A library should generate an ABI and .h files and similar files for other languages. Instead of Nim compiler trying to do it.

I see a fromFlatty for uint but not toFlatty for uint? How will this work on 32 and 64 bit systems?

I spent several hours to make ranges work, but I just get very strange and puzzling errors. I think its some sort of compiler bugs that prevent ranges from working.

This is a good start! This might be a bit much to ask, but can you also add tests, docs and parsing?

This looks like a bug. Could you provide a small example to reproduce this? You might need to include the bloom filter import in the same file as the code...

I spent several hours to make ranges work, but I just get very strange and puzzling errors. I think its some sort of compiler bugs that prevent ranges from working.

Yes you right flatty does not handle endianness that well. And yes big-endian is super rare and not worth worrying about. Its done so for speed see here: https://github.com/treeform/flatty/blob/master/src/flatty.nim#L144 An...

Sorry, I don't really support the case where you want to run the loop at 10 or 2fps. I think you are doing it correctly by going to the source...

I am working on a fidget rewrite and it will support high DPI mode. There is a UI scale parameter but you get big square pixels: https://github.com/treeform/fidget/tree/master/tests/pixelscaling