sounkou-bioinfo commented on PR #2262: URL: https://github.com/apache/arrow-adbc/pull/2262#issuecomment-3420666710
> Dear @eitsupi @paleolimbot, Adding a comment to this issue, i ve recently submitted a go using package to CRAN and it was archived because of some warnings and of interest arrow case is the build failure on windows. I have submitted a question on r-package-devel mailing list https://hypatia.math.ethz.ch/pipermail/r-package-devel/2025q4/012067.html and the feedback was as follow > > > Sounkou, > > as usual, you should start with the instructions in "External Libraries for CRAN packages"[1] which really boils down to sending an e-mail to CRAN and CCing me and Uwe. That is assuming that produced Go binaries are self-contained and don't need a run-time. If that's not the case, then it gets a lot more complicated as it would require static run-time built with R tools and that may complicate Windows support substantially (since MXE doesn't have Go AFAICS, you'd have to ask Tomas). In the simple case we can install toolchains on the build machines if they are officially available and compatible. The latter is an issue here as you pointed out so it may be worth discussing that. We may want to test things first before rolling it out. > > The way I see it, given the constraints in Go, it would be worthwhile to write something like an "Rgo" package that is the only Go runtime and any R package that wants to add Go code would use it to load its code as Go plugin. This is in concept similar to other languages like Python (reticulate) or Java (rJava) where you always load only one run-time and then simply use the corresponding language-provided loading mechanism to load any additional code/modules. This is just based on a cursory glance, so Go enthusiasts may want to comment on the feasibility. > > Cheers, > > Simon > > [1] https://cran.r-project.org/web/packages/external_libs.html > > As it appears that the adbc go using drivers are using the c-shared buildmode, i wondered if this is the reason the packages where not submitted to CRAN and if anybody ever encountered this issue [golang/go#65050](https://github.com/golang/go/issues/65050). In my use-case since i can avoid using cgo by reworking the package, therefore i may be requesting the a simple go installation on the windows machine. > > For the other "Rgo" suggestion, i wondered if there are any plans/appetite for this. And feeback from go enthusiasts is highly welcomed. > > Best wishes Thank you for the intervention and the explanation of the journey ! At least all of this can be found more easily now. The go 1.21 regression on the issue is a shame (but i guess somebody really need the "performance hack" for go users of). Also great to see that the go runtimes are isolated in the adbc packages ! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
