Skip to content

Support joker #160

New issue

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

By clicking “No 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? No Sign in to your account

Merged
merged 1 commit into from
Mar 23, 2019
Merged

Support joker #160

merged 1 commit into from
Mar 23, 2019

Conversation

arichiardi
Copy link
Contributor

@arichiardi arichiardi commented Mar 22, 2019

This patch introduces the defcustoms necessary for supporting joker.


Before submitting the PR make sure the following things have been done (and denote this
by checking the relevant checkboxes):

  • The commits are consistent with our [contribution guidelines][1]
  • The new code is not generating bytecode or M-x checkdoc warnings
  • You've updated the changelog (if adding/changing user-visible functionality)
  • You've updated the readme (if adding/changing user-visible functionality)

This patch introduces the defcustoms necessary for supporting joker.
@arichiardi
Copy link
Contributor Author

@bbatsov what do you think if we release 2.2.0 after this is in?

@bbatsov
Copy link
Member

bbatsov commented Mar 22, 2019

Oh, that's interesting. That's support for the actual Joker! First I expected to see something related to linting.

Yeah, we can cut a new release afterwards.

@arichiardi
Copy link
Contributor Author

This is pretty straightforward but I don't have access for publishing, only merging. No rush, testing it now ;)

@bbatsov
Copy link
Member

bbatsov commented Mar 22, 2019

So, everything looks good, but I'm starting to worry about our use of vars for every dialect we support, as this resulted in having a ton of them. Probably we should fold all the vars together and just have them point to an alist mapping forms to different dialects. This would also eliminate the need for all the pcases around the code - if all we had was an alist we can directly ask for the form matching our REPL type.

The only downside of this approach is that changing the defaults becomes a bit more complex, but I highly doubt that people do this often (if at all).

@arichiardi
Copy link
Contributor Author

Yeah that would require quite a bit of refactoring - I don't think I can afford it at the moment. Inf-clojure is quite low in my list of open source to contribute to. I had a bunch of time when lumo was my main runtime but ... well ... things change 😄

@bbatsov
Copy link
Member

bbatsov commented Mar 23, 2019

This is pretty straightforward but I don't have access for publishing, only merging. No rush, testing it now ;)

Btw, that's pretty much the same. Releases happen automatically when you add a tag.

Yeah that would require quite a bit of refactoring - I don't think I can afford it at the moment. Inf-clojure is quite low in my list of open source to contribute to. I had a bunch of time when lumo was my main runtime but ... well ... things change 😄

Fair enough. Let's keep it as is.

@arichiardi
Copy link
Contributor Author

Ok I will try to do it then.

So the plan is to change the CHANGELOG and commit with tag. Is that all?

@bbatsov
Copy link
Member

bbatsov commented Mar 23, 2019 via email

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

Successfully merging this pull request may close these issues.

2 participants