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

Function cr_assert_err_eq not documented properly. #229

Closed
MickaToast opened this issue Nov 7, 2017 · 5 comments
Closed

Function cr_assert_err_eq not documented properly. #229

MickaToast opened this issue Nov 7, 2017 · 5 comments
Milestone

Comments

@MickaToast
Copy link

Hi,

I've notified that cr_assert_arr_eq is not documented properly, ie the third parameter of the function is said to be " * @param[in] FormatString (optional) printf-like format string" but in fact it need to be given and must represent the size of the array.

Thanks.

@MickaToast
Copy link
Author

Seems that the issue was already reported 1 year ago #100

@Snaipe
Copy link
Owner

Snaipe commented Nov 8, 2017

Good catch! it seems that we regressed when we switched to doxygen.

@utybo
Copy link

utybo commented Oct 5, 2020

3 years later, this is still an issue fyi :D

Anything we could do to help?

@interrupt-routine
Copy link

interrupt-routine commented Sep 2, 2021

still an issue as of september 2021 :( I thought the array macros were broken and I was using cr_assert_eq(memcmp()) instead ...
To be clear, I'm talking about this : https://criterion.readthedocs.io/en/master/assert.html#array-assertions

@Snaipe Snaipe added this to the v2.4.0 milestone Jan 1, 2022
@Snaipe
Copy link
Owner

Snaipe commented Jan 1, 2022

This will be fixed by the new 2.4.0 release. Sorry for the massive delay.

@Snaipe Snaipe closed this as completed Jan 1, 2022
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

No branches or pull requests

4 participants