Should Adept support type inference?

[ghost]

It's something very useful to have. Type inference is not something specific to dynamic languages. Static typing languages still can support type inference. For example, C++'s auto.

[IsaacShelton]

Adept does not support type inference like C++'s auto keyword. In future versions, once better LSP features and proper LSP server are implemented, then there will probably be something like it.

[ghost]

Please correct me if I'm wrong, but I don't think the LSP server has anything to do with supporting type inference in the compiler.

[IsaacShelton]

It doesn't, but I mean that auto is not as useful without a good LSP as it can easily result in incorrect code which doesn't behave as expected. You often end up having to figure out what the type is anyway most of the time, even though it's not explicitly stated in your code, which is why I believe a good LSP is necessary to get the full benefits of auto.

[ghost]

Even with auto, C++ is still static typing and most of the time I could guess the type easily. C++'s type inference is not the same as the type inference of dynamic languages like Python. It's still static typing all the time. You can't possibly get lost!

[IsaacShelton]

I'm aware that auto is still static typing.

I disagree, once you start working on actually large codebases, you can easily get lost with auto if you don't have an LSP, especially once user-defined polymorphic functions get involved.

Although, most Adept codebases are pretty small so it wouldn't very bad in the short term.

I still think a good LSP should be added first though.