initialization of "int" record fields fails for unsigned integers

Description

The following script demonstrates how initialization is not consistent with
assignment for the "int" type:

Running this script gives the following result:
error in ./test.bro, line 6 and count: type clash for field "ii" ((coerce [$ii=7] to myrecord) and count)
error in ./test.bro, line 6: bad record initializer ((coerce [$ii=7] to error))
error in ./test.bro, line 10 and count: type clash for field "ii" ((coerce [$ii=7] to myrecord) and count)
error in ./test.bro, line 11 and count: type clash for field "ii" ((coerce [$ii=7] to myrecord) and count)
error in ./test.bro, line 12 and count: type clash for field "ii" ((coerce [$ii=7] to myrecord) and count)

Changing the "7" to "+7" in the script for all occurrences of "7" except the last one makes the script work as expected.

Environment

None

Assignee

Unassigned

Reporter

Daniel Thayer

Labels

None

External issue ID

None

Components

Priority

Normal
Configure