Story time When I go on vacation with a fellow Python developer, inevitably I will talk about Python. 😁 Back in September, Andrea and I drove the Cabot Trail with our friends Dusty and Jen, which led to a discussion about the match statement and how Dusty and I both wished

I’m still digesting this one and haven’t formed any strong opinions yet.

I’ve had problems in the past where this could have been useful, like ingesting millions of lat/long positions and trying to string them together in a “trail”. But, I was still able to handle that fine with namedtuple without too much pain.

Thoughts?

  • lightsecond@lemmy.world
    1·
    1 year ago

    I’m not a fan of introducing yet another “type of class”.

    In my humble opinion, if we do introduce rust-like match it should work on top of the existing concepts of dataclass, namedtuples, and union-types to avoid confusion on when to use which mechanism.

    Also, type hints aren’t compulsory, but they are so damn useful that I’d be okay if some features only worked when the original variables had type hints.