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
Introduction
Current interface may confuse because cluster_data might be used instead of concrete type (such as dbscan_data, fcm_data, etc.). As a result segmentation fault occurs. The cluster_data shouldn't be accepted by algorithms to avoid this situation, concrete implementation should be used instead. If there is no concrete implementation than alias must be created.
Description
Update algorithm interface in order to use concrete type of data instead of cluster_data.
Update unit-tests.
Look for possibilities to forbid allocation of cluster_data, for example, to make it pure abstract class with partial implementation.
Links
There is an issue that indicates problem of current interface: #576 .
The text was updated successfully, but these errors were encountered:
Introduction
Current interface may confuse because
cluster_data
might be used instead of concrete type (such asdbscan_data
,fcm_data
, etc.). As a result segmentation fault occurs. Thecluster_data
shouldn't be accepted by algorithms to avoid this situation, concrete implementation should be used instead. If there is no concrete implementation than alias must be created.Description
cluster_data
.cluster_data
, for example, to make it pure abstract class with partial implementation.Links
There is an issue that indicates problem of current interface: #576 .
The text was updated successfully, but these errors were encountered: