ccl/ccl.go, branch v0.1.1A configuration language inspired by textprotohttps://code.roseh.moe/ccl/atom/ccl.go?h=v0.1.12025-11-19T03:20:29ZHoly shit fuzzing is so cool2025-11-19T03:20:29ZRose Hogensonrosehogenson@posteo.net2025-11-19T03:20:29Zurn:sha1:933c9c9721bf20bc00dab85a75546a7573c31747Small cleanup2025-10-31T02:18:15ZRose Hogensonrosehogenson@posteo.net2025-10-31T02:18:15Zurn:sha1:4ff064043759c3b25cca2555cc50efa48c855f8aSet the lexer as a field on parser2025-10-31T02:09:35ZRose Hogensonrosehogenson@posteo.net2025-10-31T02:04:42Zurn:sha1:e4f0185460ab348d596877606b2d4a99b4c27ffb
goos: linux
goarch: amd64
pkg: roseh.moe/pkg/ccl
cpu: AMD Ryzen 9 5900X 12-Core Processor
│ baseline.txt │ new.txt │
│ sec/op │ sec/op vs base │
Parse-24 4.808µ ± 0% 4.739µ ± 0% -1.44% (p=0.000 n=20)
Use a classic struct iterator instead of iter.Pull2025-10-31T01:50:19ZRose Hogensonrosehogenson@posteo.net2025-10-31T01:45:11Zurn:sha1:aa8a935f620a053cc9c3c65587b433f3e8d3a6e9
iter.Pull doesn't provide much value here. Actually the lexer is
probably simpler this way, and iter.Pull also destroys stack traces for
panics in the lexer.
Ouch
goos: linux
goarch: amd64
pkg: roseh.moe/pkg/ccl
cpu: AMD Ryzen 9 5900X 12-Core Processor
│ baseline.txt │ itern't.txt │
│ sec/op │ sec/op vs base │
Lex-24 1.436µ ± 0% 1.320µ ± 0% -8.05% (p=0.000 n=20)
Parse-24 7.846µ ± 0% 4.801µ ± 0% -38.82% (p=0.000 n=20)
geomean 3.356µ 2.517µ -24.99%
Don't allocate an intermediate map[string]any2025-10-31T01:34:25ZRose Hogensonrosehogenson@posteo.net2025-10-31T01:29:34Zurn:sha1:74235daa0ae145c96b63c980e98c9c169f5c0007
Not too bad
goos: linux
goarch: amd64
pkg: roseh.moe/pkg/ccl
cpu: AMD Ryzen 9 5900X 12-Core Processor
│ baseline.txt │ mapn't.txt │
│ sec/op │ sec/op vs base │
Parse-24 8.880µ ± 0% 7.885µ ± 0% -11.21% (p=0.000 n=20)
Allow all values to be pointers2025-10-30T18:55:19ZRose Hogensonrosehogenson@posteo.net2025-10-30T18:55:19Zurn:sha1:3888d15001e4f6ee8319874184b78c072fca577e
This solves the issue of whether the field was populated or not, at the
expense of some horrible memory patterns. But on the plus side it
doesn't require any extra API so we might as well allow it.
Remove the regexes2025-10-30T18:35:15ZRose Hogensonrosehogenson@posteo.net2025-10-30T18:04:23Zurn:sha1:b1e37119da439b52a2c1f1aca4df2fdc80462f97
Wow it doesn't look good for regex
goos: linux
goarch: amd64
pkg: roseh.moe/pkg/ccl
cpu: AMD Ryzen 9 5900X 12-Core Processor
│ baseline.txt │ regexn't.txt │
│ sec/op │ sec/op vs base │
Lex-24 8.625µ ± 1% 1.429µ ± 0% -83.43% (p=0.000 n=20)
Parse-24 18.305µ ± 0% 8.856µ ± 0% -51.62% (p=0.000 n=20)
geomean 12.57µ 3.557µ -71.69%
Fix repeated fields behavior2025-10-29T14:26:07ZRose Hogensonrosehogenson@posteo.net2025-10-29T14:26:07Zurn:sha1:1954c6b847cd7115471cf222cee16a5e51d9c864Rename to ccl2025-10-29T03:34:39ZRose Hogensonrosehogenson@posteo.net2025-10-29T03:34:39Zurn:sha1:2ffdc8b3ded7173a01a91359b730064f3b4ab17c
It stands for "cute configuration language," but idk if that's
really important
Rename files to ccl2025-10-29T03:32:44ZRose Hogensonrosehogenson@posteo.net2025-10-29T03:32:44Zurn:sha1:e084ac2b84fac3b5ae63de15080b863d31f5b2fc