From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 5990 invoked from network); 1 Dec 2023 16:38:31 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 1 Dec 2023 16:38:31 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 9front; Fri Dec 1 11:37:11 -0500 2023 Message-ID: Date: Fri, 01 Dec 2023 17:37:00 +0100 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: <963d0ca4-518a-40a1-b95a-bc96ed9595a6@app.fastmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: database singleton-aware ActivityPub over XML cloud proxy Subject: Re: [9front] [PATCH] Correct acid's rune size to 4 bytes Reply-To: 9front@9front.org Precedence: bulk > I think I want to switch this back to hardcoding 4 bytes > instead of using sizeof on the basis that > a) the rune size is probably not going to change again any time soon > b) if it *does* acid would then be inconsistently wrong instead of consistently wrong > c) consistency with the rest of the acid codebase. > Opinions? yeah, i agree with all your points. -- cinap