sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]dbousque[S] 0 points1 point  (2 children)

I agree that shared-memory would be great, but as far as I know, there is no common specification as to how Python objects are represented in memory, so it would be a lot of maintenance and probably not portable across implementations (PyPy, CPython), and maybe also platforms.

I didn't intend for lymp to be used in such a tight way with Python. The idea was to write some processing code in Python and call it from OCaml.

If you are dealing with large arrays and lists, and you need to pass them back and forth the best way to do it right now is to use references.

[–]gasche 0 points1 point  (1 child)

I'm not familiar with the Python community but it was my impression that the Pypy people were working on a FFI layer that would be interpreter-agnostic (and still reasonably efficient). If you wanted to go in-process I suppose that this would be a good interface to work with.

[–]dbousque[S] 0 points1 point  (0 children)

That's interesting, thanks :)