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

hal::bit_modify::insert with unhelpful error message when a signed integer is used as a parameter #3

Open
FluffyFTW opened this issue Feb 21, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@FluffyFTW
Copy link

FluffyFTW commented Feb 21, 2024

Right now, when trying to bit_modify insert takes the mask and a uint32_t as parameters. When an integer is being placed in the uint32_t parameter, you would get the error: 'no matching function for call to hal::bit_modify<long unsigned int>::insert(hal::bit_mask&, int). This can be confusing when trying to insert a set integer such as error: no matching function for call to

hal::bit_modify<long unsigned int>::insert(bit_mask, 0b11);

vs

hal::bit_modify<long unsigned int>::insert(bit_mask, 0b11U);

If we could get a more descriptive error message that would be very much appreciated.

@kammce kammce changed the title bit_modify::insert with unhelpful error message when a signed integer is used as a parameter hal::bit_modify::insert with unhelpful error message when a signed integer is used as a parameter Mar 9, 2024
@kammce kammce added the bug Something isn't working label Mar 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants