Bicep treating ints as signed 32-bit values instead of unsigned 64-bit.

[WhitWaldo]

Bicep version
0.4.1008

Describe the bug
I'm typing out an object in my Bicep file. Two of the fields require that I enter an int64 number. According to the documentation:

In Bicep, integers are 64-bit integers.

However, that isn't stopping a red squiggly from being drawn under my value in VS code with the error:

Expected a valid 32-bit signed integer. bicep(BCP010)

To Reproduce
Type in something like the following in a Bicep file in VS Code:

var myValue = -9223372036854775808

Additional context
The only workaround I've got to this so far is doing the following:

var myValue = int('-9223372036854775808')

[anthony-c-martin]

Note that this problem only exists for -9223372036854775808 - all other int64 numbers are expressible in Bicep.

• int64.MinValue == -9223372036854775808
• int64.MaxValue == 9223372036854775807
• I believe the problem arises because we interpret -9223372036854775808 as 0 - 9223372036854775808, but 9223372036854775808 is not a valid int64 as it's greater than int64.MaxValue.

[anthony-c-martin]

Also - as part of the fix, we should address the wording of the error: "Expected a valid 32-bit signed integer. bicep(BCP010)" should say "Expected a valid 64-bit signed integer. bicep(BCP010)"