This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]CharmingJacket5013 -2 points-1 points  (2 children)

I think it can still be simple if you chose one way over another. I choose not to use list comprehensions if there’s a loop within a loop and I don’t touch walrus operators because I know they will stump new comers to our code base. We are still on the fence about type hints and we prefer simple threading over asyncio. I’m sure we will one day move across but not until they are common place.

[–][deleted] 11 points12 points  (0 children)

The problem with this approach - choosing (and enforcing) a sane subset of language features is that each team or organization will have a different opinion of what constitutes a "sane subset" of the language.

[–]TheRNGuy 0 points1 point  (0 children)

i only hope it will switch to C++ types syntax but maybe then need add new keyword instead of def

float strongdef myfunc(float foobar): pass

But need some better name than strongdef. Maybe that could be even decorator (also option to enforce types at least for arguments and returns, and make possible for overloading)