Simon Albrecht <[email protected]> writes: > On 06.10.2017 22:00, David Kastrup wrote: >> Simon Albrecht <[email protected]> writes: >>> Hello, >>> >>> for the first time in a while I’m doing some actual LilyPond work and >>> noticed the following ‘loophole’: neither our docstring on >>> ly:assoc-get nor the guile-1.8 reference manual entry on assoc say >>> whether they always check the keys in the alist in order, i.e. what >>> happens if there are multiple entries with the same key. >>> >>> What does it do? >>> >>> And should we add that info to said docstring? >> Always checked in order to that you can override by adding stuff in >> front (which is the only directly accessible locus of a list). > > Well, if you append two alists, you can do it either way, that’s why I > was asking. > Anyway, to repeat my second question, is it just me to whom this > wasn’t obvious or should it be documented?
It's pretty well-defined for Scheme. But if we have a ly:assoc-get of our own, it might make sense mentioning it in there. Most other places talking about alists, probably not so much. -- David Kastrup _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
