addItemsCol,getAllNNsCol andgetAllNNsListCol are thecolumn-based equivalents ofaddItems,getAllNNs andgetAllNNsList, respectively.Note that the returned nearest neighbor data fromgetAllNNsCol andgetAllNNsListCol arealso stored by column, i.e. the matrices have dimensionsk x n wherek is the number of neighbors, andn the number of items in the data being searched.byrow hasbeen added tohnsw_knn,hnsw_build andhnsw_search. By default this is set toTRUEand indicates that the items in the input matrix are found in each row.To pass column-stored items, setbyrow = FALSE. Anymatrices returned byhnsw_search andhnsw_knnwill now follow the convention provided by the value ofbyrow: i.e. ifbyrow = FALSE, the matricescontain nearest neighbor information in each column.getItems, which returns a matrix of thedata vectors in the index with the specified integer identifiers. From afeature request made byd4tum (https://github.com/jlmelville/rcpphnsw/issues/18).progress parameter in the functional interface nolonger does anything. Whenverbose = TRUE, a progress baris no longer shown.setNumThreads method if using the object-based API, and then_threads parameter in thehnsw_* functionAPI. For finer control, asetGrainSize andgrain_size option is also available in the object andfunction interface respectively. Thank you toDmitriy Selivanov for a lot ofthe work on this.verbose = TRUE now has incurs substantiallyless computational overhead associated with calculating the progressbar. Thank you toSamuelGranjeaud for spotting the problem and coming up with varioussolutions.progress. By default this is set to"bar" and will show the progress bar whenverbose = TRUE. If you want a more terse output, setprogress = NULL.progress = NULL willeventually be the default setting: for now,verbose = TRUEwill get you the progress bar by default for backwardscompatibility.markDeleted, that will remove an objectfrom being retrieved from the index.resizeIndex, that allows the index to beincreased without having to save and reload the index.size is available for the index objectsand reports the number of items added to the index.hnsw_search wouldstop if the number ofrows in the input matrix was smaller thank. This check hasbeen removed. Note that the correct behavior is to ensure thatk is smaller than or equal toindex$size()whereindex is the index you are searching. Because thesize() method is new to this version, to preservecompatibility with old indexes, this checkhasn’t been added tohnsw_search. If this matters to you, manually compareindex$size() withk before runninghnsw_search. An error will be thrown ifkneighbors can’t be found in the index. Thank you toYuxing Liao for spotting this andthe pull request to remove the check.Initial release.