Geert Janssen

I would love to see some more algorithm documentation: what is the approach you take, what do the main functions do, what are the assumptions in terms of existing Torch...

I understand that it is not easy to piggy-back on existing Torch routines and be able to handle the diverse suite of "layers" all correctly. I am glad to see...

I added "-fpermissive" to the compiler options in setup.py and got it to build. Not sure if that is really a solution though.

Same for me on CentOS 6.10 using g++ 4.8.2. A pity. I added "-fpermissive" to the compiler options in setup.py. Now it compiles but the tests give me 10 fails...

Thanks, that's all I wanted: to be able to see the UUID assigned to the Android app. Good luck with your rewrite work.

Dear Y. Somda, thanks for the extensive answer. I am very familiar with TF and have build many models for it and also converted them to TF-Lite. It is just...

And I just learned that also BLOCK_ENTRY is printed both in case of FYTT_BLOCK_ENTRY and FYTT_FLOW_ENTRY. I assume the latter must print FLOW_ENTRY?

I am just pointing out what I think to be minor errors in the code. They probably would not affect regular use. But I am interested to use fy-tool to...

In master libfyaml/src/tool/fy-tool.c: ``` case FYTT_BLOCK_ENTRY: if (colorize) fputs(A_BRIGHT_CYAN, stdout); printf("BLOCK_ENTRY"); break; case FYTT_FLOW_ENTRY: if (colorize) fputs(A_BRIGHT_YELLOW, stdout); printf("BLOCK_ENTRY"); ```

Same file fy-tool.c: ``` case FYTT_KEY: if (colorize) fputs(A_BRIGHT_YELLOW, stdout); printf("KEY"); break; case FYTT_VALUE: if (colorize) fputs(A_BRIGHT_YELLOW, stdout); printf("KEY"); ```