Closed piyo closed 6 years ago
Thanks for your feedback :)
I've gone through and added the seq.el functions that I think make sense. Note that some of your additions are dangerous -- you should not be adding higher-order functions like seq-mapcat
into suggest-functions
. Suggest.el can find arbitrary functions with read
, so if I have an input of "delete-file"
then you really don't want it to try things like (seq-mapcat (read "delete-file") (list 1 2 3))
.
You can use suggest-funcall-functions
for these and it should be safe.
Suggest.el doesn't really work with macros, so I've not added seq-doseq
. I've also skipped functions that take predicates, as users tend not to supply predicates as inputs and suggest.el usually refuses to try predicates to avoid executing something with side-effects. I also skipped a couple of trivial functions like seq-length
that don't seem like useful additions when we already have length
. suggest.el is pretty much O(N) in the size of suggest-functions
.
Other than that, there are some great functions that suggest.el definitely benefits from. As you showed, suggest.el hasn't been very good at vectors and this really helps improve in that area. :) I've also added a few entries in suggest-extra-args
to make the most of these new functions.
I hope that make sense! I'm happy to discuss any further additions you think I've missed.
Thank you very much for your consideration and also for the extra comments. (^_^)/
Hello, what an intriguing package.
Personally I want to see recommendations from the seq.el library as well.
To start this off I am looking over each function and comparing the results to the default suggest.el configuration. The following is an in-progress skeleton.
Before (without seq.el):
After (with seq.el):