Fix class declaration hoisting and typeof double-evaluation

[lahma]

• fix class declaration hoisting (to actually make it hoist)
• fix typeof evaluating value (getter) when only reference should be retrieved, has perf benefit too
• marking now failing module tests as skipped, need to be addressed in Module support fixes and improvements #1102

/cc @christianrondeau

[sebastienros]

It hurts somewhere, but I can't locate it

[sebastienros]

It's equivalent to return d is VariableDeclaration v && v.Kind == VariableDeclarationKind.Const; right?

[lahma]

yup, takes some time to digest, but it's quite nice syntax, like is/are both these true - type and it's property values

[lahma]

I'm going to merge this with green build as there's test coverage and this is not much of rocket science...

[sebastienros]

So a class can't be used until declared? That's the opposite of hoisting, right?

[lahma]

well class needs to be registered during script initialization, like anything in lexical scope, then later on it will be initialized to correct value and access before initialization (JintClassDeclaration runs) should cause reference error. Now earlier it was considered undefined as it hadn't even been registered until the JintClassDeclaration runtime.