Right now, we only recognize and handle the number type, which can be either an int or float.
There are many places in WFLang (especially in builtin params and method return types) where it definitely matters whether a number value is an int or float. Furthermore, int and float are themselves recognized types in WFLang that have methods.
This is a change that will need us to think all the way along the stack from the lexer through to user-facing features such as hovertexts.
The longer we leave this, the more difficult it's going to be to implement.
Right now, we only recognize and handle the
numbertype, which can be either an int or float.There are many places in WFLang (especially in builtin params and method return types) where it definitely matters whether a number value is an int or float. Furthermore, int and float are themselves recognized types in WFLang that have methods.
This is a change that will need us to think all the way along the stack from the lexer through to user-facing features such as hovertexts.
The longer we leave this, the more difficult it's going to be to implement.