Python with Braces

Re:Python with Braces by __MatrixMan__ on Sunday July 07, 2024 @10:48PM (#40902211)

Last time I looked, [Unison code] -> [entry in the AST DB] was a one-way process. Adding a function means writing it (with whatever style you like) and seeing if what you wrote constitutes a new function or an existing one. You can't fluff db entries back up in to human friendly code.

I don't see why it couldn't be done though, I think it just hasn't been a priority. Heck, you could have 100 different users collaborating in 100 different "languages", and so long as they serialized to the same AST and back, none of them would ever have to see the atrocious syntax which the other users prefer. Their editors and browsers could just render everything according to their users' preferences.

Edit: it appears that Unison has an issue for this feature: https://github.com/unisonweb/unison/issues/499

[ Parent | on HN ]

Re:Python with Braces by tkzed49 on Sunday July 07, 2024 @10:55PM (#40902232)

if they were truly represented by the same AST, I can't believe the differences between these "languages" would be anything more than swapping symbols out.

[ Parent | on HN ]

Re:Python with Braces by __MatrixMan__ on Monday July 08, 2024 @12:54AM (#40902705)

True. Perhaps "styles" or "syntaxes" would be better. It's all that stuff we spend time building consensus around, but that doesn't affect program behavior. If our tools respected our style preferences on a user-by-user basis, we could drop the consensus requirement altogether.

[ Parent | on HN ]