Q: When I tried comparing transducers.el to cl-lib and dash (benchmark-compiled), I got the following results
Q: Do you know of any theoretical texts on transducers?
Q: Did you think about [compiler features, macros] viz your cl, fennel, elisp, porting of your transducers?
Q: Does t-buffer-read provide a lazy stream that\'s linewise, or charwise, or do something else entirely?
Q: Can the Elisp library be combined with the stream.el API or seq in general?
Q: How does one debug a t-comp expression? Can you single step and see intermediate results of the different statements you declare?
Q: Is there a path for transducers to enable elisp processing of otherwise overly large datasets as if just normal Emacs \"buffers\" (i.e. just pulling one thing at a time so essentially stream-like under the hood but buffer-like in interface), with none of the usual perf issues with a traditional buffer structure?
Q: Is there an option to read a csv/json and produce an alist or plist instead of a hash table for an entry?
Q: Is the common lisp version ready for 'production' use? Is it complete enough and the API stable enough?
Q: Do we need a pre-written \"t-\" version for every already existing reducing function like + or is there a function to construct them from already defined reducer 2-arg functions?
Q: Is the compelling argument for transducers is that it's a better abstraction?