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

linter reference implementation #47

Open
bmatsuo-at-luthersystems opened this issue Jun 22, 2021 · 0 comments
Open

linter reference implementation #47

bmatsuo-at-luthersystems opened this issue Jun 22, 2021 · 0 comments

Comments

@bmatsuo-at-luthersystems
Copy link
Contributor

The elps command should implement a linter that can be used directly or used as a reference for implementing linters specific to the application domain elps is being embedded into.

There is one proposed use case for a linter, with docstrings in #46. Other examples would be guarding against direct use of set or using set! when there is no matching variable in scope (though the latter may be better implemented in the long term as a 'compile time' check -- which doesn't exist currently as an elps concept). Another valid concern is attempts to use the in-package operator when not in the package's top-level.

Certainly there are other gotchas which could be detected without too much effort. But the ones discussed here probably merit including a default linter implementation with the project.

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

1 participant