Currently, packages pass optional additional arguments down to their respective build systems using a somewhat clunky pattern which includes the type tg.MaybeNestedArray<T>. Design and implement a cleaner strategy, and ensure this type does not appear in any top-level user-facing interface.
One strategy we briefly discussed was to split the tg.Args argument parsing step out from the actual build logic for each interface that employs the variadic argument pattern.
Currently, packages pass optional additional arguments down to their respective build systems using a somewhat clunky pattern which includes the type
tg.MaybeNestedArray<T>. Design and implement a cleaner strategy, and ensure this type does not appear in any top-level user-facing interface.One strategy we briefly discussed was to split the
tg.Argsargument parsing step out from the actual build logic for each interface that employs the variadic argument pattern.