[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNU ELPA] New package: tam
From: |
Lynn Winebarger |
Subject: |
Re: [GNU ELPA] New package: tam |
Date: |
Wed, 20 Sep 2023 12:44:26 -0400 |
On Wed, Sep 20, 2023 at 12:07 PM Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
> Any reason why you're not using `cl-defstruct`?
See my last response to Philip Kaludercic.
> Also, is it important to document that the values returned from
> `tam-allocate` (and passed to `tam-free/tam-table-get`) are integers?
I'm only committed to those functions returning an "index" that can be
created in constant time. Since there is no facility for multiple
return values without some kind of consing, that pretty much means a
fixnum. I have at least considered making the integer return value
into a bitfield split between a slot number and some kind of
"generation number" recorded in each slot, so free-after-free errors
with an intervening reallocation could be caught. That would be
over-engineering at this point, but I wouldn't commit to never
providing it as an option.
Maybe I should rename tam-table-get to just tam-get now that the table
and pool structures overlap.
Lynn
Re: [GNU ELPA] New package: tam, Adam Porter, 2023/09/18
Re: [GNU ELPA] New package: tam, Stefan Monnier, 2023/09/20
- Re: [GNU ELPA] New package: tam,
Lynn Winebarger <=