This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
@cfleming: I'm using a 'conciseness' macro that accepts a binding form as an argument (i.e without the surrounding
fn). The problem is, Cursive marks all the symbols I define in this binding form as 'unable to resolve', and I end up with a lot of warnings. Is there any way to combat this?
@val_waeselynck: Yeah, as explained in that issue Cursive still has a problem with macros.
I suppose the inability of Cursive to get the source code (F4) for some things like
set! is a known limitation?