A recent release of Free Pascal has a rather interesting behaviour for its list implementation. Lists grow additivitely (rather than multiplicatively) above 128MiB, trading off computational complexity for trying to avoid out-of-memory issues!
https://wiki.lazarus.freepascal.org/User_Changes_3.0.4#TList_auto-growth
miniblog.
Related Posts
Really elegant developer tool: Go's inline IDE feature is used with deprecation markers, so call sites are autofixed from OldApi() to NewApi() based on the implementation of OldApi.
Is there a good term for "after using this feature we realised that the best design is different from the current design"?
In casual conversation I generally hear "bug" but there was nothing wrong with the original implementation.
I've been working on a search tool for a website with 9K items and a dumb implementation works just fine. I'd normally gravitate to a library or tool like elasticsearch (ES).
Adding custom filters etc is trivial on handrolled code. I wonder what scale requires actual search infra like ES.