beam_reorder: Don't confuse beam_validator

Make sure we don't optimize code such as:

  is_tuple Fail Src
  test_arity Fail Src Arity
  get_tuple_element Src Pos Dst
  is_map Fail Src

If we would reorder the instructions like this:

  is_tuple Fail Src
  test_arity Fail Src Arity
  is_map Fail Src
  get_tuple_element Src Pos Dst

beam_validator would complain that the type for Src is a map
instead of a tuple. Since the code has problems to begin with,
there is no need to do the optimization.

0 files changed, 0 insertions, 0 deletions