You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My primary reason for using Python / C interoperability was that I made experience on the whole range from utter failure to successful cross-platform bindings. I think the main issue is that there is no definite guide for language bindings, once you figured it out you keep it until it breaks down, but there are some common pitfalls and techniques which are useful to know for all interfacing scenarios. Therefore, the target language shouldn't matter that much.
Still, I think having a good template, build system wise, to also show Fortran, C and R interoperability might be worth exploring. I'm doing my building for Fortran, C and Python all in meson, because Python build systems are really lacking for dealing with more than Python as language (also there is a new Python build system like every month, but none has yet solved the problems I'm usually dealing with). I wonder whether this is easier in the R ecosystem (I have used R a few times, but never went down the rabbit whole to build my own extension modules). Probably won't make it in til Thursday, though.
Nice logo idea, I'm currently going with a more circular one ;)
Hi Sebastian, @awvwgk
Adding some examples with R seems like a good idea. After all, R has a large audience.
A logo, :)
The text was updated successfully, but these errors were encountered: