beam_call_types: Infer the type for `band` more aggressively

For expressions such as:

    Unknown band 42

the type would conservatively be assumed to be any integer.

Be less conservative and assume that the type is an integer
in the range 0 .. 42. That will give more opportunities for
the JIT to eliminate type tests.

Note that for:

    Unknown band 0

we will still infer the type to be any integer instead of the integer
0. The reason is that code such as:

    foo(Unknown) ->
        Unknown band 0.

would be rewritten to:

    foo(Unknown) ->
        Unknown band 0,
        0.

if we were to assume that `Unknown band 0` is 0. This is a
pessimization.

0 files changed, 0 insertions, 0 deletions