Re: Gap analysis
Jonas Hahnfeld via Discussions on LilyPond development <[email protected]> Sun, 10 May 2026 14:38:54 +0200
| Newsgroups | gmane.comp.gnu.lilypond.devel |
|---|---|
| Message-ID | <[email protected]> |
On Sun, 2026-05-03 at 20:00 -0400, Dan Eble wrote: > For changed syntax/properties/functions (incl. public Scheme) > - [ ] `convert-ly` rules (`$REPO/python/convertrules.py`) (either adding to the function for the current VERSION or creating a new one if that doesn't exist yet) > - [ ] updates to existing docs and tests (incl. `\version` value) (reflecting the current VERSION) > - For new user-facing syntax/properties/functions (incl. public Scheme) > - [ ] automated regression tests (reflecting the current VERSION) This is from the fear that LLMs will base their proposal on existing conversion rules and tests that, by definition, will exist for older versions... Disclaimer: I don't actually know how "good" LLMs would be in that regard.
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRiF4DLRvon1vw5biCcVOmY/6OEDwUCagB8XgAKCRCcVOmY/6OE D3/2AQCjnu551F6P7cR6Ye5YUmZYl2Sd3kER2SnT3PP0wgtNcQD7BO0ziVf3hAfN eAB6fLFTvjf1VUtrSwd1WhrIK3T/Uwg= =HLIE -----END PGP SIGNATURE-----