#2 Add binary analysis

[CatalinStratu]

No description provided.

[pombredanne]

Thanks!
Rather than an opaque 17MB testfile.exe, can you instead commit some source code that will be compiled to an exe during the tests, possibly with separate script.
We need a test too.

Also can you commit a proper go.mod and not only a go.sum?

[pombredanne]

Thanks!
Can you add a CHANGELOG and add your name to the authors list?

[CatalinStratu]

@pombredanne now we managed to change Gore with GoReSym. Now I am waiting for the code review.

[pombredanne]

Thanks! we need to setup tests, automated tests. And build too.

[pombredanne]

Thanks! Can you avoid committing a binary? Instead build it as part of the test suite run.

[pombredanne]

I think you need to add some Makefile or script to build things correctly and run tests locally too.
This should take care of building a test exe.... that should not be committed.

[pombredanne]

Why not run just go build -v?

[pombredanne]

You cannot run the tests as part of the documentation workflow. Either create a new workflow or use the azure pipeline instead.

[pombredanne]

Can you keep your package names all lower case? Use underscore as separator

[CatalinStratu]

Can you give me a little more details?