44
Statically Typed Functional Programming with Python 3.12
(wickstrom.tech)
Welcome to the Python community on the programming.dev Lemmy instance!
Past
November 2023
October 2023
July 2023
August 2023
September 2023
I don't think I would call this functional. Python is decidedly not at all functional - there's no way to declare arbitrary functions inline, no chaining of map/filter etc.
But the static types are definitely welcome. I didn't know about the
type
keyword. Apparently it makes it support forward references.like everything in python, to achieve functional you must first
import functional
(not even a joke)
You're still limited by lambda expressions though. And in general the language is still statement based, not expression based. You can't do
a = if foo then x else y
type things (except for the one-off and backwardsx if foo else y
; they were so close!)."a = x if foo else y" is a perfectly cromulent statement!
It's not. In functional languages there's no special case like this. All if-elses are expressions. It's far superior. For example how do you do this with Python's if-else expression?
x = foo(y:=bar(), baz(), y) or z
should work assuming foo bar and baz are functions being called?if this is setting y to the effect of bar() + running baz after, then:
x = [bar(), baz()][0] or z
might work
and if you need y to be defined for later use:
x = [(y:=bar()), baz()][0] or z
but thats from memory, not sure if that will even run as written.
foo
isn't a function, it's a bool. But in any case, as you can see the answer is "with terrible hacks". Python is not a functional language. It is imperative.Yeah, never said it was, just that if you really want to emulate that style you mostly can.
Does it have higher-order functions? Yes, therefore you can use it to do functional programming.
Everything else is syntactic sugar.
Functional programming doesn't just mean higher order functions. There's a range of other features that it implies.