I was browsing the official packages and noticed an issue. The wiki says to file an issue on the specific package, but issues seems to be disabled on (all?) of the official packages. I presume that's coming from GitHub's default for forked repos, but probably not what you want.
FWIW, the original issue that caught my attention is that google-flatbuffers should have multiple targets: at least one binary for the flatc compiler and one library--just like the bazel BUILD file. Compiling the main into a library isn't going to end well :)
Hello again, awesome LoopPerfect folks,
I was browsing the official packages and noticed an issue. The wiki says to file an issue on the specific package, but issues seems to be disabled on (all?) of the official packages. I presume that's coming from GitHub's default for forked repos, but probably not what you want.
FWIW, the original issue that caught my attention is that google-flatbuffers should have multiple targets: at least one binary for the flatc compiler and one library--just like the bazel BUILD file. Compiling the main into a library isn't going to end well :)
Thanks, Chris