Hi,
Ryan Prior <rpr...@protonmail.com> skribis:
> I think there's an opportunity to avoid the need to "fall back" to the status
> quo, though. I picture a structure for inputs that has three cases, trivially
> decided based on data shape:
>
> - a bare symbol, eg '(tzdata glib)
> this is translated to `(("tzdata" ,tzdata) ("glib" ,glib))
> works the exact same if the symbol is an =origin=, you get the name of the
> symbol quoted followed by the value of the symbol.
A “bare symbol” cannot be translated into a reference to a variable in
the way you write.
I’m leaning towards either the new style:
(list glib tzdata)
or the old style:
(("tzdata" ,tzdata) ("glib" ,glib))
but not a mixture of both, which would require more code to be properly
interpreted, leading to slowdowns on the hot path and generally making
it more difficult to interpret what’s in there.
Thanks,
Ludo’.
