Re: Efficiency of alist vs. vector/array

Urs Liska writes: > Am 19.07.2017 um 10:43 schrieb David Kastrup: >> Urs Liska writes: >> >>> Obviously I didn't make myself clear enough and probably I should have >>> invested the time for a minimal example. When sloppily using the word >>>

Re: Efficiency of alist vs. vector/array

Am 19.07.2017 um 10:43 schrieb David Kastrup: > Urs Liska writes: > >> Obviously I didn't make myself clear enough and probably I should have >> invested the time for a minimal example. When sloppily using the word >> "override" I didn't mean "\override" but applying a

Re: Efficiency of alist vs. vector/array

Urs Liska writes: > Obviously I didn't make myself clear enough and probably I should have > invested the time for a minimal example. When sloppily using the word > "override" I didn't mean "\override" but applying a value to a grob > property in a grob callback function. >

Re: Efficiency of alist vs. vector/array

Obviously I didn't make myself clear enough and probably I should have invested the time for a minimal example. When sloppily using the word "override" I didn't mean "\override" but applying a value to a grob property in a grob callback function. I have a data structure idTweaks, currently using

Re: Efficiency of alist vs. vector/array

Urs Liska writes: > What I do *not* know is: would that be worth it (apart from the > educational value) in real life? In that project I had a song of a few > pages containing about 5.600 IDs. It's not clear how many override > that would get when finished, but let's assume