News for hackers. Stuff that matters.
Re:Bio – experimental Lisp dialect, written in Zig by xigoi on Sunday July 14, 2024 @04:46PM (#40963114)
There is no ambiguity with significant whitespace.
Re:Bio – experimental Lisp dialect, written in Zig by Out_of_Characte on Monday July 15, 2024 @01:34AM (#40965516)
There is, four abstractions down,my comment gets squished as a sardine
Re:Bio – experimental Lisp dialect, written in Zig by zelphirkalt on Monday July 15, 2024 @04:58AM (#40966255)
Problem is always when you need to move code, select/highlight code, paste code, navigate code, and so on. With clear start and end markers like open and close parentheses or like "begin" and "end" in other languages, that problem does not even exist.
Re:Bio – experimental Lisp dialect, written in Zig by xigoi on Monday July 15, 2024 @05:01AM (#40966275)
Those actions have never been a problem for me. Maybe get a better editor?
Re:Bio – experimental Lisp dialect, written in Zig by zelphirkalt on Monday July 15, 2024 @06:20AM (#40966580)
Basically, you are confirming, what the original comment said. I now strongly suspect, that you have never used structured editing, which is where the issues with Python syntax are.

Where paredit for Python?

Re:Bio – experimental Lisp dialect, written in Zig by xigoi on Monday July 15, 2024 @06:26AM (#40966600)
When using structured editing, why does it matter what the syntax is? The editor is going to handle it for you anyway.

> Where paredit for Python?

I don’t know, go make it. But what would you imagine it to do? Moving blocks of indented code around is already easy without needing language-specific treatment.

Re:Bio – experimental Lisp dialect, written in Zig by zelphirkalt on Tuesday July 16, 2024 @08:24PM (#40981526)
> When using structured editing, why does it matter what the syntax is? The editor is going to handle it for you anyway.

It matters, because the start and end markers of code allow for easy recognition of where something starts and ends and make the move independent from things like indentation. In Python, if you wanted to do the same, you would have to change indentation in many cases. Also the language is less expression based, which makes it even harder to, for example slurp a block/unit of code, because it is not clear how far the slurping should go.

> I don’t know, go make it. But what would you imagine it to do? Moving blocks of indented code around is already easy without needing language-specific treatment.

Well, I am not the one claiming here, that it does not matter, whether there are start and end markers for blocks of code, so the onus is not on me to make this thing, it is up to you to prove it can be done. Lets not try to reverse the obligation of proof here.