cdd31dd27b
internal/rosa/azalea: integer arrays
...
This is useful for some helper functions. Performance is unaffected.
Before:
BenchmarkStage3-128 8308 1960687 ns/op 1023794 B/op 14755 allocs/op
BenchmarkAll-128 3331 5518571 ns/op 2902320 B/op 37993 allocs/op
After:
BenchmarkStage3-128 8330 1946273 ns/op 1023046 B/op 14750 allocs/op
BenchmarkAll-128 3296 5585805 ns/op 2901746 B/op 37991 allocs/op
Signed-off-by: Ophestra <cat@gensokyo.uk >
2026-05-21 22:47:41 +09:00
1acb5b0105
internal/rosa: extra inputs in alternative path
...
This works around particularly unwieldy build systems.
Signed-off-by: Ophestra <cat@gensokyo.uk >
2026-05-21 15:05:12 +09:00
443a7a30f6
internal/rosa: use string pair for files
...
This is a much cleaner representation than the separator syntax.
Signed-off-by: Ophestra <cat@gensokyo.uk >
2026-05-21 14:07:20 +09:00
3010a209b5
internal/rosa/azalea: pass through source ident
...
For source handle special case.
Signed-off-by: Ophestra <cat@gensokyo.uk >
2026-05-19 18:10:11 +09:00
0360e779f3
internal/rosa: initial azalea bindings
...
Supported fields are still rather minimal, but evaluation works, and resulting artifacts cure correctly.
Signed-off-by: Ophestra <cat@gensokyo.uk >
2026-05-18 02:56:38 +09:00
f24ae21af1
internal/rosa/azalea: package special case
...
This is more efficient for the inputs array and packages in general.
Signed-off-by: Ophestra <cat@gensokyo.uk >
2026-05-17 23:49:19 +09:00
c2ff9c9fa5
internal/rosa/azalea: evaluator
...
Performance is sufficient for the use case, despite the fact that I could not even think of a lower-effort way to do this:
BenchmarkParse-128 55100 21494 ns/op
BenchmarkEvaluate-128 131670 9248 ns/op
Signed-off-by: Ophestra <cat@gensokyo.uk >
2026-05-17 12:44:34 +09:00
d38d306147
internal/rosa/azalea: ast and parser
...
This syntax is not final, but acts as a stopgap solution and a proof of concept.
Signed-off-by: Ophestra <cat@gensokyo.uk >
2026-05-16 14:29:28 +09:00
