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
Or something of the sort. I guess this method is only expecting list results from lisp, rather than the native CL vector type. Does there need to be some additional conversion functions written to handle vector types, or is there already something that supports this conversion?
Further, round tripping of values doesn't seem to be supported for CL vectors either.
CL-USER> (setq x (april:april-c "1 2 3 + 1 2 3"))
#(246)
CL-USER> x
#(246)
CL-USER> (april:april-c "{⍵+⍵}" x) ;; add vector x to itself using an april function#(4812)
In the above example, x is store, then passed into the next expression. but using clj, x is said to be an org.armedbear.lisp.SimpleVector and yet I can't pass it back into an expression expecting a lisp vector
defining an 'x' variable on clj and passing it CL will return a JVM address to the function on CL and april absolutely will not be able to work on that.
But I think the request does make a lot of sense and it is worth to try to add support for org.armedbear.lisp.SimpleVector on the cl->clj conversion. I'll try to do it this week.
Is there a way presently to convert Common Lisp vectors to Clojure vectors? Especially the higher dimensional variety?
For instance
Or something of the sort. I guess this method is only expecting list results from lisp, rather than the native CL vector type. Does there need to be some additional conversion functions written to handle vector types, or is there already something that supports this conversion?
Further, round tripping of values doesn't seem to be supported for CL vectors either.
In the above example, x is store, then passed into the next expression. but using clj, x is said to be an
org.armedbear.lisp.SimpleVector
and yet I can't pass it back into an expression expecting a lisp vectorThe text was updated successfully, but these errors were encountered: