Fix lexer to tokenize triple '<' properly

[barthez]

It was producing [<<, <] but it should [<, <<]. Added lexer rule with push back to fix it.

I was having troubles with dialyzer formatter to parse: <<<_:8,_:_*1>>,'false'>

[codecov[bot]]

Codecov Report

Merging #44 into master will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #44   +/-   ##
=======================================
  Coverage   86.01%   86.01%           
=======================================
  Files           1        1           
  Lines         143      143           
=======================================
  Hits          123      123           
  Misses         20       20

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 35986f7...cd0ee37. Read the comment docs.

[barthez]

Related to

• https://github.com/jeremyjh/dialyxir/issues/383
• https://github.com/jeremyjh/dialyxir/pull/384
• https://github.com/phoenixframework/phoenix/issues/3697

[asummers]

I will have to test this later. I worry this will choke on e.g. <<<x,y>, z>, w> type inputs and we need to be smarter.

[asummers]

I think this instead needs to be solved by removing << and >> a lexed characters and then <<x>> needs to be parsed separately instead.

[asummers]

Thank you for the proposed fix! :purple_heart:

I stole your test in #45. I wound up removing some of the parsing tokens instead of adding a new token to the lexer.