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

Error/lint on non-use of return values once purity is completely tracked #20

Open
calebzulawski opened this issue Apr 17, 2023 · 2 comments

Comments

@calebzulawski
Copy link
Collaborator

I just spent some time debugging a simple case where I meant to write ^func args and instead had func args

@afranchuk
Copy link
Collaborator

Yeah this would be very easy if the function is known to be pure. Unfortunately if the function is impure the same mistake can be made :( If there were more type information (static analysis) available, there could be a lint that warns when e.g. a function returns a map but isn't being merged.

@calebzulawski
Copy link
Collaborator Author

Good point, checking the type would probably be better. This seems like a relatively lightweight check, some lints like this could probably be turned on by default (without specifically enabling linting)

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

2 participants