💾 Archived View for bbs.geminispace.org › u › undefined › 22046 captured on 2024-12-17 at 15:50:15. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Re: "Pitfalls of structure editors"
Yeah, lisp is really the best case scenario for these kind of things since the syntax is just a direct representation of the ast. Though that simplicity comes with restrictions on that very ast: one of the reasons you don't have explicit typing in lisp, for example, is not that you can't do it, it's that it would be a pain to write and deal with so people just through inertia end up rolling with a worse system. And, as you've said, the macros break that uniformity anyway.
Nov 22 · 4 weeks ago
Pitfalls of structure editors — The tools for a structure-aware editing have existed for a long time in IDEs and things like tags, cscope and lsps as of late, as well. However, the editors fully commited to this kind of mindset haven't really been done well before. Here, I'll list some of the reasons I myself have found while trying to design one, later abondoning the project. Also, while I am myself pessimistic of this idea, it would be interesting to hear other perspectives, or inspire...