While NaN is considered to be type number in most programming languages, Hopscotch doesn’t really have an intended way to show NaN, and the player parses it as a string type , not a number type. This should be consistent in the editor.
example: NaN + 3 = NaN in most languages, but Hopscotch treats NaN like a string, so it results in NaN3 ↩︎
So, does that mean we want to parse the strings NaN and Infinity as numbers if a user sets variables to those strings? If that’s the case, I agree and we should file an issue in the webplayer for that. Otherwise, if they’re still going to be treated as normal strings when a user enters those, then the bug is in the editor.