Skip to content

Conversation

@ethanglaser
Copy link
Member

No description provided.

@ahuber21
Copy link
Contributor

I'm not a fan of the conditionals in the API. We already have a runtime check if a storage kind is supported. That is, requesting e.g. LVQ_4x4 on non-Intel will throw a runtime error. We can do the same if LVQ/LeanVec wasn't even compiled in. All interfaces, however, should look the same.
All downstream code must compile with either version (LVQ/LeanVec enabled vs. disabled).

Copy link
Contributor

@ahuber21 ahuber21 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The API should not be affected by whether or not LVQ/LeanVec was enabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants