fix: handle ellipsis before <-, ::, and when (#114)

Ellipsis standalone detection used is_binary_op?/1, but that set did not
include in_match_op, type_op, or when_op. As a result, expressions like
x...<-y and x...::y attempted to parse <-/:: as an ellipsis RHS prefix
and failed with unknown token errors.

Extend @binary_op_types with when_op, in_match_op, and type_op so
parse_ellipsis_op/1 keeps ... standalone before those operators,
matching Elixir AST behavior.

Add regression assertions in the existing property regression block for
x...<-y, x...::y, and x... when y alongside the newline ternary case.

Author: mkaput

lib/spitfire.ex

@@ -1757,6 +1757,9 @@ defmodule Spitfire do
     :rel_op,
     :arrow_op,
     :in_op,
+    :when_op,
+    :in_match_op,
+    :type_op,
     :xor_op,
     :ternary_op,
     :concat_op,

test/spitfire_test.exs

@@ -2316,6 +2316,10 @@ defmodule SpitfireTest do
       assert Spitfire.parse("x...\n;//y") == s2q("x...\n;//y")
       assert Spitfire.parse("x...\n;\n//y") == s2q("x...\n;\n//y")
       assert Spitfire.parse("x...\n;\n# comment\n//y") == s2q("x...\n;\n# comment\n//y")
+      # Ellipsis followed by infix operators that should not be consumed as RHS
+      assert Spitfire.parse("x...<-y") == s2q("x...<-y")
+      assert Spitfire.parse("x...::y") == s2q("x...::y")
+      assert Spitfire.parse("x... when y") == s2q("x... when y")
     end
   end