Posts: 4,647
Threads: 1,494
Joined: Sep 2016
i'm making a new abstract data type. it might exist, already. it is a list that expands as items are stored to it. if the location already exists, it replaces what is there. it not, it expands the list (virtually). you can get what's there at any time. it keeps data in a sparse way, allowing the caller to see extents of data and holes, including the highest and lowest extents. can you tell me what to name this or what the existing name is?
Tradition is peer pressure from dead people
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.
Posts: 4,647
Threads: 1,494
Joined: Sep 2016
Dec-01-2019, 08:53 PM
(This post was last modified: Dec-01-2019, 08:59 PM by Skaperen.)
but with this one, you can store into any position even beyond its current length.
skaplist.store(data,1000000)
puts
data
at position 1000000 leaving a sparse gap up to there. it will also do negative positions.
i think i will implement it with a tree structure.
Tradition is peer pressure from dead people
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.
Posts: 4,647
Threads: 1,494
Joined: Sep 2016
there will mostly be ranges of indexes being filled. that is it might put data into [64] through [255]. there might also be negative ranges. it might leave out every Nth item in a few cases (if this overlaps, then previous data remains in those "holes"). the underlying implementation might be a dictionary or something more optimal in the future.
once it is filled in, access is mostly in a similar sequence as before ... same ranges in different orders.
an "infinite" list would work. if accessing an index that was never filled in, it gets the established default.
Tradition is peer pressure from dead people
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.