Skip to content

Warn on incorrent keyword/named arguments with flycheck #1654

@sarna

Description

@sarna

What do you think about warning the user about calls like these?

(defn named [&named arg] # I used &named here but same goes for &keys
  (print arg))

(named :arg "hi") # correct
(named :arrgh "this will not print") # wrong

I can't think of any case when the user would want this, and it should be detectable before running the code.

Splicing would be out of scope of this issue (e.g. (named ;(kvs options))).

For more context - Zulip thread. I originally opened this issue in the janet-lsp project, but seems like this would be a better place for it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions