Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Marking functions with associated specs #1842

Open
olivergeorge opened this issue Sep 7, 2017 · 2 comments
Open

Marking functions with associated specs #1842

olivergeorge opened this issue Sep 7, 2017 · 2 comments

Comments

@olivergeorge
Copy link

I'd like to know which of my functions have a (s/fdef ...) spec associated with them so that I'm encouraged to add ones which are missing.

A simple visual indication would be enough to be useful.

@danielcompton
Copy link
Collaborator

Also, when an fdef is added to a function, it marks the function as being used, even if nothing else in the project references it.

@danielcompton
Copy link
Collaborator

One more thing I noticed with fdef, it is valid (and maybe even better style, ala core.typed) to have it declared above a function, but Cursive shows a not resolved warning if you do it this way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants