Matus Goljer

The `VAL` here is `'(3)` is non-nil, which passes. The list matching was done on purpose like this, where you can match prefixes or extra keys. That happened before `if-let`...

Oh yea, so I got myself confused. What you say is correct. The `-if-let` requires all the destructured variables to be non-nil, not the "source". What I said was not...

Hi Ivan. This is something I haven't considered but it shouldn't be terribly difficult as you say. One would need to make sure the recursive expansions would still work, but...

@yyoncho I will merge this today, I promise!

I tried ``` (let (var) (cl-callf '->> var 1 (* 2) (+ 1)) var) ``` and I get `Debugger entered--Lisp error: (invalid-function '->>)`

I see, yes that works. I like it.

`-let` can destructure `nil` fine ```elisp (-let (((&plist :foo foo) (list :foo nil))) foo) ``` but you are using `-when-let` which fails if any binding is `nil`, that's probably the...

Is there any reason why you have multiple signatures ```elisp ((type number &keys :salted salted) (type &keys :salted salted) (type number) (type) :defaults ((number 10) (salted t))) ``` I assume...

About the stricter version, that actually might be quite difficult, because the `nil` check is handled in `-if-let` not in the internal `dash--match` function which does the expansion. And `-if-let`...

@alphapapa Not really no, I struggle with those myself. They are handled in quite annoying way. I think it would still be better to maybe invent a notation where we...