On Wed, Feb 22, 2017 at 10:51 AM, Yann Ylavic <ylavic....@gmail.com> wrote: > > For example, the attached patch uses the seprator ", " (quite HTTP > field inspired), but it could be a json string or whatever... > We could also have an explicit tostring/tojson() function which would > stringify anything as argument. > > Or yet more operators on lists, like list_empty(), list_first(), > list_last(), list_nth(), list_match(<list>, <regex>) (returning > another list of matching entries), ... you name it. > > Working on anything from a certificates looks very useful at least. > > WDYT?
+1. What does the list evaluate to prior to the fix? Seems like regression risk is low (sophisticated expression with lists that don't ever return what you'd expect). Otherwise I'd suggest we give users e.g. list_join() and just add a few examples. -- Eric Covener cove...@gmail.com
