<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engineering In-place (Shared-memory) Sorting Algorithms · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2009.13569/</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/2009.13569/feed.xml" rel="self" type="application/rss+xml" /><item><title>Engineering In-place (Shared-memory) Sorting Algorithms — mentioned by scott_s</title><link>https://news.ycombinator.com/item?id=28220758</link><guid isPermaLink="false">urn:hackerpapers:mention:2009.13569:28220758</guid><pubDate>Wed, 18 Aug 2021 13:36:48 GMT</pubDate><description>&lt;p&gt;Academic paper: &amp;quot;Engineering In-place (Shared-memory) Sorting Algorithms&amp;quot;, Michael Axtmann, Sascha Witt, Daniel Ferizovic, Peter Sanders, https://arxiv.org/abs/2009.13569 To start discussion, I think it&amp;#x27;s interesting to note how I landed on this repo and paper. I got curious about Tim Sort, and some searching on HN brought up a 2018 story, &amp;quot;On the Worst-Case Complexity of TimSort&amp;quot;, https://news.ycombinator.com/item?id=17883461. In the comments, poster lorenzhs has an excellent comment (https://news.ycombinator.com/item?id=17884612) which points out IPS4o as a sorting algorithm that takes…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2009.13569/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DC</category></item></channel></rss>
