A few notes on choosing between Go and D for a quick project

[Laeeth Isharc via Digitalmars-d]

On Tuesday, 17 March 2015 at 21:00:11 UTC, bachmeier wrote:
> On Tuesday, 17 March 2015 at 19:00:06 UTC, jmh530 wrote:
>> In addition, further development of the ability to call D from 
>> R or Python* or Julia (or vice-versa) would also be a positive.
>
> What do you have in mind? I no longer work much with Python so 
> my knowledge is limited, but calling D from R or Julia should 
> be no different from calling C from those languages, as you 
> normally compile your C code into a shared library anyway.
>
> I've done the R->D thing many times and in the process have 
> worked with a big chunk of the R API. Things like allocating R 
> data structures from a D function, adding assertions to your D 
> code to allow for an easy exit when things don't work out, and 
> calling functions in the R math library, among other things, 
> are not difficult.

PyD is pretty nice, although one wouldn't want to call it from an 
inner loop.  And it's easy to go via cython also.  (I wonder how 
well cython works with interfacing with D via the C++ interface, 
because that way you could extend python with D classes and have 
them be faster than going through PyD).

PyD also works with numpy memoryviews I think.

For Julia, easy to call D.  It would be nice to port julia.h to D 
(I started, but got distracted) so D can call back Julia.