cursive 2021-09-14 | Slack Archive

Hello, it seems that Cursive cannot resolve x in this type of destructuring while it seems valid in Clojurescript.

(let [[x
       {:keys [y]
        :or {y x}}
       {:keys [z]
        :or {z x}}] [:a nil {:z :c}]]
  [x y z])
=> [:a :a :c]

imre10:09:47

same in clojure

thumbnail18:09:13

Afaik this is undefined behaviour in Clojure: https://clojurians-log.clojureverse.org/clojure/2020-03-02/1583165149.094200

Vincent Cantin03:09:52

@UHJH8MG6S That's very instructive, thank you.

markaddleman15:09:23

I would love for search to support fully qualified symbols and keywords. I found this issue https://github.com/cursive-ide/cursive/issues/821 which, I think amounts to the same thing. If it doesn't, I'll open a new issue

greg16:09:38

I've noticed a "x cannot be resolved" warning when using async `alt!`. I believe syntax is correct, it works, still Cursive highlights it. What do you think?

greg12:09:15

#Also sent to the channel

Is there any way of disabling selected "cannot be resolved" highlights like these?

greg12:09:15

replied to a thread:I've noticed a "x cannot be resolved" warning when using async `alt!`. I believe syntax is correct, it works, still Cursive highlights it. What do you think?

Is there any way of disabling selected "cannot be resolved" highlights like these?

2021-09-14

Channels