<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>From Tool Calling to Symbolic Thinking: LLMs in a Persistent Lisp Metaprogramming Loop · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2506.10021/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2506.10021/feed.xml" rel="self" type="application/rss+xml" /><item><title>From Tool Calling to Symbolic Thinking: LLMs in a Persistent Lisp Metaprogramming Loop — mentioned by wfn</title><link>https://news.ycombinator.com/item?id=46666402</link><guid isPermaLink="false">urn:hackerpapers:mention:2506.10021:46666402</guid><pubDate>Sun, 18 Jan 2026 09:59:03 GMT</pubDate><description>&lt;p&gt;I&amp;#x27;ve been thinking about this, take a look at this: &amp;gt; From Tool Calling to Symbolic Thinking: LLMs in a Persistent Lisp Metaprogramming Loop https://arxiv.org/abs/2506.10021 edit but also see cons[3] - maybe viable for very constrained domains, with strict namespace management and handling drop into debugger. Also, after thinking more, it likely only sounds nice (python vs lisp training corpus and library ecosystems; and there&amp;#x27;s mcp-py3repl (no reflection but otherwise more viable), PAL, etc.) Still - curious. In theory (I&amp;#x27;ve seen people discuss similar things before though), homoiconicity…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2506.10021/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item></channel></rss>
