Subject: bug#32841: assoc-set fails with dot notation association list

From: Tomas Volf <[email-masked]>
Date: Mon, 21 Oct 2024 22:26:48 +0200

".%c2.п." via "Bug reports for GUILE, GNU's Ubiquitous
Extension Language" <[email-masked]> writes:

> The thread and all replies were in 2018. Six years later, in 2024, Anyone opening the up-to-date online manual still sees the old bad code there! The manual is not adjusted even though previous emails had pointed the cause and solution out!
> Today, the page has a valid link of&nbsp;         https://www.gnu.org/software/guile/manual/html_node/Alist-Example.html&nbsp;&nbsp;and&nbsp;still contains
>
>          6.6.20.6&nbsp; Alist Example
>
> Here is a longer example of how alists may be used in practice.
> (define capitals '(("New York" . "Albany")                    ("Oregon"   . "Salem")                    ("Florida"  . "Miami"))) ;; What's the capital of Oregon? (assoc "Oregon" capitals)       ⇓ ("Oregon" . "Salem") (assoc-ref capitals "Oregon")   ⇓ "Salem" ;; We left out South Dakota. (set! capitals       (assoc-set! capitals "South Dakota" "Pierre")) capitals ⇓ (("South Dakota" . "Pierre")     ("New York" . "Albany")     ("Oregon" . "Salem")     ("Florida" . "Miami")) ;; And we got Florida wrong. (set! capitals       (assoc-set! capitals "Florida" "Tallahassee")) capitals ⇓ (("South Dakota" . "Pierre")     ("New York" . "Albany")     ("Oregon" . "Salem")     ("Florida" . "Tallahassee")) ;; After Oregon secedes, we can remove it. (set! capitals       (assoc-remove! capitals "Oregon")) capitals ⇓ (("South Dakota" . "Pierre")     ("New York" . "Albany")     ("Florida" . "Tallahassee"))
>
>
>
>  
>
>               
>                                                 深圳大学                                  
>                                                                     陈
>                                                 有骏

Your message is really hard to read, I cannot make heads or tails of the
formatting.  Could you please resend it formatted in a normal way?  In
particular, wrapping your text to 72 characters and properly formatting
the code example will improve the readability a lot.

Have a nice day,
Tomas Volf

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.