Should travis ci failures be ignored? Or do we know why they happen?

CI failures shouldn't be ignored, since master works fine.

@makenowjust Looks good, thanks!

I think the slash_is_regex! thing is good, but I got it wrong that it belongs to the parser. The lexer should already know when a next token can be a regex or a division. So after the = token (ignoring any non-newline whitespace that comes next) / will never mean division, always regex.

So those slash_is_regex! calls should be in Lexer, not in Parser.

I plan to do this refactor later. But maybe we can just create an issue about this and if someone wants to tackle this they can go ahead (it could be @makenowjust but it could be anyone, really). It should be relatively simple given that there are plenty of tests for crystal's parser and lexer.

What do you think?

(in the meantime we could merge this because it's already an improvement)