Skip to content

Drop usage of set_feature_matrix - #4376

Merged
vigsterkr merged 5 commits into
shogun-toolbox:developfrom
vinx13:cleanup/drop_set_feature_matrix
Aug 15, 2018
Merged

Drop usage of set_feature_matrix#4376
vigsterkr merged 5 commits into
shogun-toolbox:developfrom
vinx13:cleanup/drop_set_feature_matrix

Conversation

@vinx13

@vinx13 vinx13 commented Jul 17, 2018

Copy link
Copy Markdown
Member

now the only usage of set_feature_matrix is swig

$self->set_feature_matrix(new_feat_matrix.clone());

after that we can drop it from public api

@vinx13

vinx13 commented Aug 1, 2018

Copy link
Copy Markdown
Member Author

an idea to deal with swig is to use a friend function, so that we can hide set_feature_matrix from public api, @karlnapf what do you think

@karlnapf

karlnapf commented Aug 3, 2018

Copy link
Copy Markdown
Member

I think that is a good idea, depending on where this statement will be.
The alternative in such special cases is to use put<SGMatrix<T>>("feature_matrix", mat)

@vinx13
vinx13 force-pushed the cleanup/drop_set_feature_matrix branch from 4e34014 to 1686180 Compare August 6, 2018 12:11
@vigsterkr
vigsterkr merged commit aab0812 into shogun-toolbox:develop Aug 15, 2018
ktiefe pushed a commit to ktiefe/shogun that referenced this pull request Jul 30, 2019
* Make set_feature_matrix protected
* Use put instead set_feature_matrix in swig
* Call tag-version put
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants