Parser error, i think

[lortonx]

Parser error, i think

[CountBleck]

I'm not sure if AS supports typeof yet.

[HerrCai0907]

I'm not sure if AS supports typeof yet.

yes. typeof will return a string of object type

[lortonx]

I'm not sure if AS supports typeof yet.

The problem is not even that, the problem is an error in the parser. Unfortunately, I didn’t check the typeof, but I saw that this have checks in tests https://github.com/AssemblyScript/assemblyscript/blob/main/tests/compiler/typeof.ts

[HerrCai0907]

I have token a look about this issue. It is because parser handle alignof< typeof 1 > (); as Identifier LessThan Expression GreaterThan NotFinishedFunctionExpression.
It is hard to distinguish generic and lessThan and greaterThan operator without semantic analysis. But unfortunately, we will not do any semantic analysis in parser stage.

[CountBleck]

typeof x when used as a type is parsed separately and differently from typeof x when used as an expression. For instance, typeof x(), typeof (x), typeof x[a ? b : c], and so on are parser errors in TS.

I suspect that typeof for types hasn't been implemented yet.

[CountBleck]

The error you reported indicates the parser expected code like this, which is seen as (y < typeof x) > ((): i32 => 0), without the extra parentheses.

Edit: @HerrCai0907 beat me to it by 6 minutes and I didn't notice.

[HerrCai0907]

Interesting thing is TS also have similar problem.
true<false>(true); is valid but let a=true;a<false>(true); is invalid.

[CountBleck]

It is hard to distinguish generic and lessThan and greaterThan operator without semantic analysis.

Semantic analysis isn't necessary. TypeScript eagerly parses generics (which makes sense; practically no one would write a < typeof b, let alone a < typeof b > () => ... or a < typeof b > (c))

Interesting thing is TS also have similar problem.

You actually brought up what I typed above as I was typing it. 😆
Calling it a problem is a bit of an exaggeration, and true is probably treated specially as a keyword, thereby causing that case to be valid. It's not a major issue, since true < false > (true) is a generally useless expression.