A lot of people would love to see that happen, not for the sake of this situation, but for the sake of being able to translate C to Go in moderately large projects and general uses. If you or someone else has a way to do that, then that would be very interesting to see.
Having said that, I think there is also a point here about the use of C-isms in a Go code base. We are writing Go code, not C/C++ code. There are likely things we can do with Go to make the library and APIs much nicer to use. And I would like to see that instead of just translating libtiff or libraw. On Thu, Aug 11, 2016 at 2:10 AM, Cristian Măgherușan-Stanciu < cristi.magheru...@gmail.com> wrote: > What if the libraw C codebase would be converted to Go using the same > approach done when the golang compiler was translated to go? > > -- > You received this message because you are subscribed to a topic in the > Google Groups "golang-nuts" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/golang-nuts/60WthPS_TXg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
