Is gleam a subset of Python?

[pwtail]

Hi @lpil

I happen to be a Python developer, and I think noticed a thing: is gleam a subset of Python? Python has added the match..case statement in 3.10 for pattern matching, with types, guards and everything.

Of course, Python is not a functional language, so if, for and match are not expressions, but simply blocks. But other than that?

Yes, I know, Jose already used the Ruby syntax. But he copied the OOP part, which he shouldn't! By no means! :)

[lpil]

Hi @pwtail ! No, Gleam is not a Python subset, it is very different in many ways. I would be happy to go into any details you may be interested in.

[pwtail]

If you don't mind... then what are the parts missing from Python? I have found one thing myself, that is the pipeline operator. Will you find more?) ср, 8 мар. 2023 г., 15:48 Louis Pilfold ***@***.***>:

…

Hi @pwtail <https://github.com/pwtail> ! No, Gleam is not a Python subset, it is very different in many ways. I would be happy to go into any details you may be interested in. — Reply to this email directly, view it on GitHub <#2057 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD2OEIAIK7JQRA7VTI52ZM3W3CL4RANCNFSM6AAAAAAVTYFHTA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[lpil]

Other language features include the static type system, compile time resolution of function argument labels, tail call optimisation, different semantics for pattern matching, use expressions, and a very different syntax that will allow things like multi-statement lambda functions. If you look at the runtime, the tooling, and the ecosystem there are further differences too, and there are many features that Python has that Gleam deliberately does not.

[pwtail]

and there are many features that Python has that Gleam deliberately does not.

That's why I used the word "subset". The runtime is different too, there is no doubt about it. I've read somewhere the inspiration for the "use" keyword was the python's 'with', so I didn't count it. ср, 8 мар. 2023 г., 16:03 Louis Pilfold ***@***.***>:

…

Other language features include the static type system, compile time resolution of function argument labels, tail call optimisation, different semantics for pattern matching, use expressions, and a very different syntax that will allow things like multi-statement lambda functions. If you look at the runtime, the tooling, and the ecosystem there are further differences too, and there are many features that Python has that Gleam deliberately does not. — Reply to this email directly, view it on GitHub <#2057 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD2OEIFILLXZZMMTR7CNPVLW3CNUVANCNFSM6AAAAAAVTYFHTA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[lpil]

While with was one of the influences use is very different and more flexible. If anything one of the things that inspired use was my frustrations with how limited with is in Python 😁

[pwtail]

Sorry I feel I'm being very rude right now. The first thing is that gleam does things just right and I'm very impressed. ср, 8 мар. 2023 г., 16:12 Абеткин Виталий ***@***.***>:

…

>and there are many features that Python has that Gleam deliberately does not. That's why I used the word "subset". The runtime is different too, there is no doubt about it. I've read somewhere the inspiration for the "use" keyword was the python's 'with', so I didn't count it. ср, 8 мар. 2023 г., 16:03 Louis Pilfold ***@***.***>: > Other language features include the static type system, compile time > resolution of function argument labels, tail call optimisation, different > semantics for pattern matching, use expressions, and a very different > syntax that will allow things like multi-statement lambda functions. If you > look at the runtime, the tooling, and the ecosystem there are further > differences too, and there are many features that Python has that Gleam > deliberately does not. > > — > Reply to this email directly, view it on GitHub > <#2057 (reply in thread)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AD2OEIFILLXZZMMTR7CNPVLW3CNUVANCNFSM6AAAAAAVTYFHTA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[pwtail]

Python has decorators, on the other hand) ср, 8 мар. 2023 г., 16:41 Louis Pilfold ***@***.***>:

…

While with was one of the influences use is very different and vastly more powerful. If anything one of the things that inspired use was my frustrations with how limited with is in Python 😁 — Reply to this email directly, view it on GitHub <#2057 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD2OEICBBZDACIIBOP7LAZ3W3CSB5ANCNFSM6AAAAAAVTYFHTA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[lpil]

Python's decorators are also very limited, being just another syntax for function calls. In Gleam you can achieve the same with use.

[pwtail]

Yes they are. However it is tempting to make a gleam remake with python syntax. Please tell me something to rethink this :)

[lpil]

Sounds like it could be a fun project!

[pwtail]

Or it will be useless. If there are no new ideas to bring in, why start it?

Soon there will be the necessity to break the python syntax (to let use pattern matching inside the if statement, for example). So, soon it will be invalid python code anyway. So is the gleam code currently.