feat: add bitmath inspector

[shellcromancer]

Description

This adds a new bitmath inspector similar to the strings inspector focused on comparison operations with numbers. The supported operations are and, or, xor, and not and compare the resulting value with 0.

Motivation and Context

Some datasets have field which are bitfield constants where the meaning is best unpacked with bitwise masking to check values and then inserting the meaning into a new field. I don't believe this is possible to check with the other inspectors today.

How Has This Been Tested?

New test cases have been added to cover the new existing operations and it solves for the target use case internally.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[jshlbrd]

Overall looks good, added some comments for small improvements and requests for more unit testing.

Would this ever need to support floats?

[jshlbrd]

What happens if the data isn't a number? I think this needs a unit test, too.

[shellcromancer]

I switched the parsing to be a little looser with size and format of interpretation by interpreting the byte slice input as a string, then parsing that string to a number using strconv.ParseInt and return an error when this condition is used without numeric input.

[shellcromancer]

Overall looks good, added some comments for small improvements and requests for more unit testing.

Thanks for the quick review! :) Made some changes including the additional unit tests 👍

Would this ever need to support floats?

Today this inspector would handle floats in a loss-y way by truncating values into integers. There might be a use case for float handling considering that the JSON spec supports decimal notation (specifically arbitrary-precision decimal), but it's implementation should live separately b/c the key operation of bitwise-and masking isn't defined on floats in Go.

[jshlbrd]

Today this inspector would handle floats in a loss-y way by truncating values into integers. There might be a use case for float handling considering that the JSON spec supports decimal notation (specifically arbitrary-precision decimal), but it's implementation should live separately b/c the key operation of bitwise-and masking isn't defined on floats in Go.

It sounds like two different inspectors (number and bitwise) or this one inspector handles the value differently depending on the type.

[shellcromancer]

It sounds like two different inspectors (number and bitwise) or this one inspector handles the value differently depending on the type.

With that in mind I've focused this on doing bitmath and then comparing for a non-zero result instead and removed non-bitwise types 👍

[jshlbrd]

Approved and changes look good! I added some comments that should be addressed before merging. Could you also change the PR name to be more reflective of the new direction?