← Back to context

Comment by ameliaquining

3 months ago

I don't think it's optimizing for beginner-level code, I think it's optimizing for legacy code. Introducing a type checker to a large existing untyped codebase is a big lift, but becomes less of one if almost all existing code is accepted.

3 comments

ameliaquining

Reply
luoc  3 months ago

Well then support an option to enable that kind behaviour? Make it an explicit decision by the devs. I think running in a type error and then adding an exception to your config is safer than silently pass and only learn about the mixed types in a production bug

  • shoeb00m  3 months ago

    I think this should be handled by a type assisted linter not typechecker.

    Imo a type checker in a dynamic language should is primarily there to avoid runtime errors. In a list with multiple types the typechecker should instead force you to check the type before using an element in that list.

    If you want static types python is the wrong language