Issue #3542

Closes #3513

Not 100% sure that this is the best way to deal with this - but if
you're in an expression, and encounter what you think is a type, it's
probably better to change your assumption and treat it as you would a
variable/constant (Because that's what it probably is) rather than to
forget everything.

I ran the test suite, and it didn't break anything, and the linter,
which was quiet.

Closes #3504

(not *totally* confident about its correctness, but it looks like a
plausible fix, and seems to work ok)

Closes #3500

I don't know if

1) there's a way to get haxe to, while in functiondef, for instance,
   be able to tell the compiler that what it thought was a type name
   is actually a variable name, and to indent/highlight correctly

or

2) there's a way that, assuming it's a type name, to still indent
   correctly

but it is possible to loosen the lexer to accept things marked as
types as function names (in functiondef), and this fixes the
indentation problem.

Closes #3494

Closes #3492

Bumping them for every release just adds too much git
noise and history blowup.

Haxe supports imports with willcard
http://haxe.org/manual/modules#import-whole-package

IE<9 does some truly messed-up things when it sees these.

Another great JS feature banished for the foreseeable future by
the bunglers in Redmont, sigh.

As spotted by the extended linter.

 - Background parsing now never goes past the visible part of the
   document.

 - We only store style information for lines that are actually visible
   (and then keep it cached).

 - When the document changes, background highlighting always
   re-highlights from the change to the end of the visible part.

 - Gets rid of compareState mode methods and the hairy heuristic that
   tried to simulate it when absent.

 - The onHighlightComplete callback was removed, since it no longer
   really applies -- the document is only fully parsed when scrolled
   to its end.

This should help preserve memory (a huge document will no longer
immediately have parser state and highlighting information built up
for all lines, but only for the parts that you look at), and removes
the pathological case when you, for example, are typing at the top of
a huge XML document, and opening or closing a tag causes a whole
re-highlight to cascade all the way to the bottom because the
compareState will detect a change.

Issue #688

Add CodeMirror.defineOption function for defining new options.

Add findMatchingBracket to the methods exported by this extension.

Closes #746

* Remove ":" from electricChars
* Add compareStates function
* Add keyword "using"
* Fix anonymous type

This mode is based very heavily upon the javascript mode.