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
Fix most compiler warnings #1086
Conversation
Yep. How I missed this is beyond me. I'll do that update myself. |
👍 Great work! Now it's time for the big fun cider-interaction split. |
btw, do you know what causes all of the |
Most likely it's cask. //cc @lunaryorn |
@bbatsov I'm not sure what I'm supposed to say here… Cask doesn't compile, and if I'm to take a look at these warnings, I'd at least like to see them somewhere. |
Gets us partway to #875. This is pretty weird though:
cider-eval-buffer
is defined here but is then aliased tocider-load-buffer
here. The alias was added to fix #865 - I guess for now we should just deletecider-eval-buffer
and keep the alias? If/when the source-tracking eval patch is merged to nREPL we can look into making the distinction between eval and load more clear, and have these as separate commands again.The following warnings will require more significant restructuring of things, mostly handled by #1068: