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?

  • @[email protected]
    4•1 year ago

    Opinion: This doesn’t really solve a problem like dataclasses v. namedtuples did. This mostly boils down to someone not really liking the dataclass syntax and deciding that adding yet another way to write classes is the way to go and is somehow more teachable (because now we need to teach both).

    Maybe it’d be nicer in a few use cases, but I don’t really feel it’s worth the expansion to the syntax burden.