I'm not familiar with the process nor with the tools that were used, but I guess there are people on this list who may be able to point you to those. I suppose if it was feasible for something as large and complex as a compiler, it should be much easier for comparatively smaller pieces of software like this kind of library. As for the C-isms, those can be refactored over time, making the code closer to idiomatic go.
The problem with converting such libraries to Go is mostly philosophical, related to the fact that there may be other software written in C/C++ and other languages using them out there, and many other languages can use C/C++ libraries through bindings but those may not exist for software written in Go. Making a library in Go might render tools written in other languages unable to use the Go version of the library, and it would eventually cause fragmentation and duplication of effort, which may not be desirable. -- 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.
