97jaz

The complexity of the merge algorithm is given in Okasaki and Gill as worst case O(m+n).

@jeapostrophe The line continuations (the slash line followers) in `match l \` and `mac timed \` seem visually odd to me, seeming to suggest that the match expression (or macro...

@jackfirth says: > It means you never have to guess whether a variable is being `set!` or not. True, though I imagine in the first case, you'd do pretty well...

> Can't the primary concern about `set!` be dealt with simply by overriding its definition to trigger an error whenever it is used? In a word, no: 1. I don't...

> In fact, if you want to do static analysis, set! is far preferable than box because box is a value which can flow dynamically. set! on the other hand...

> Question about Option 1: what will happen if someone annotates a variable as mutable, but use it immutably? Is it considered an error? I never considered that. My inclination...

I think the problem is more generally with unicode combining characters: ``` #lang racket/base (define chars '(#\e #\u0301)) (displayln chars) (displayln (list->string chars)) (newline) (define precomposed-chars ((compose string->list string-normalize-nfc list->string)...

Related? https://github.com/racket/draw/issues/22 According to a comment in this issue, DrRacket always uses `#f` for the `combine?` parameter to the `draw-text` method of `dc`. And the code has this comment: https://github.com/racket/draw/blob/a4e156abe5119309783443495d671b9a7f3e434b/draw-lib/racket/draw/private/dc.rkt#L1493

I also think performance of generics is important -- and not just in the long term. People won't use them if they're too slow. And if people start by not...

Struct instance constructors? They used to follow the `make-` convention but they haven't for a long time. (Circa Racket 5.0, maybe?)