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

Return nil responses instead of default behavior (exception?) when info is missing. #7

Closed
gtrak opened this issue Feb 19, 2014 · 3 comments

Comments

@gtrak
Copy link
Contributor

gtrak commented Feb 19, 2014

Makes cider just hang. Can work around by C-g.

@bbatsov
Copy link
Member

bbatsov commented Feb 20, 2014

Returning nil seems preferable as we can handle it properly in cider.

@bbatsov
Copy link
Member

bbatsov commented Mar 3, 2014

Alternatively we can return an empty list.

@dgutov
Copy link

dgutov commented Mar 3, 2014

The eval-ing functions usually receive information about whatever misfortune happened. Maybe the ops should return it, too.

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

No branches or pull requests

3 participants