Skip to content
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

[FEA] rename ASSERT in error.hpp to RAFT_ASSERT #2462

Open
hsgui opened this issue Sep 30, 2024 · 3 comments
Open

[FEA] rename ASSERT in error.hpp to RAFT_ASSERT #2462

hsgui opened this issue Sep 30, 2024 · 3 comments
Labels
feature request New feature or request

Comments

@hsgui
Copy link

hsgui commented Sep 30, 2024

Is your feature request related to a problem? Please describe.
I wish I could use RAFT together with another thirdparty library. but the redefine of ASSERT in error.hpp will cause the compiling issue as ASSERT is just so common used.

for example gperftools also has its own macro define ASSERT in internal_logging.h

Describe the solution you'd like
Could we just rename the ASSERT to something like RAFT_ASSERT?

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context, code examples, or references to existing implementations about the feature request here.

@hsgui hsgui added the feature request New feature or request label Sep 30, 2024
@hsgui hsgui changed the title [FEA] change ASSERT in error.hpp to RAFT_ASSERT [FEA] rename ASSERT in error.hpp to RAFT_ASSERT Sep 30, 2024
@cjnolet
Copy link
Member

cjnolet commented Sep 30, 2024

Hi @hsgui,

Thanks for opening an issue about this. We have had a long standing todo to remove the ASSERT macro in RAFT altogether since we have been using RAFT_EXPECTS for some time. We will go ahead and remove this for our next release (24.12)

@hsgui
Copy link
Author

hsgui commented Sep 30, 2024

@cjnolet thanks for your replying.

May I ask when will our next release be? Maybe I could make a pull request to replace ASSERT with RAFT_EXPECTS?

thanks again

@cjnolet
Copy link
Member

cjnolet commented Sep 30, 2024

Thanks @hsgui. Pull requests are always welcome and that would be a great way to get more familiar with the contributions process if you are interested.

We release every 2 months on the CalVer scheme, so our current release 24.10 will be released in October, however we already entered code freeze for this release and so it’s too late to add changes. The next release is 24.12, which will be released in December.

But that doesn’t mean users have to wait until December before packages are available because we release new nightly packages after every PR is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
Development

No branches or pull requests

2 participants