New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove NArray from ruby typemap #4178
Comments
@karlnapf I am interested in this issue. For array, we can replace NArray.xxx($arguments) for example with Array.new($arguments){xxx(0) }, is that okay? I also had a look at Ruby's Matrix library (The one in std-lib now) and it looks like the matrix is actually immutable, so once it is initialized, it can't be assigned since the [] operator is private. (The author of Ruby said he will make it mutable in the future) One workaround to this is to use: Would that be okay to replace NMatrix.xxx()? And if so, I'd have to slightly edit the translate.py file so that it passes in addition $numRows, $numColumns (and $arguments) so that I can set the ruby.json as: Array.new( $numRows ){Array.new( $numColumns ) {0} } If that sounds good then let me know and I'll start working on it. |
Hey. |
@FaroukY |
@songxujing pls dont spam this thread which is about something else. Pls use the mailing list or open a new issue. |
Ruby these days supports matrices natively, so no need to do this with the unmaintained narray.
This task is to re-write the typemap such that the new in-built matrices/vectors are used.
The meta example integration tests serve as a reference -- they can only pass if the typemap works correctly. The task is quite nontrivial, but there is a lot of existing code to guide the way, so still a good first issue
The text was updated successfully, but these errors were encountered: