GRID IN operator has different results in 8.x than 7.x

Description

At version 7.x, the IN operator returns zero, whereas at 8.x, it returns NODATA.

Cause

The documentation for IN states the following:

"If the ... value ... is not contained in the set specified by the second input, the location will receive NODATA on the output grid."

The result in version 7.x is erroneous.

Solution or Workaround