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

[WIP] Refactor and improve Common Lisp client #348

Closed
wants to merge 1 commit into from

Conversation

Dotrar
Copy link
Contributor

@Dotrar Dotrar commented Apr 27, 2022

This PR is to improve the Common Lisp client, mainly by refactoring the code and making it easier to read, and changing to the slynk client that is a more modern and maintained version of slime for common lisp.

TODO:

  • Confirm Slynk message encoding/decoding in remote.transport.slynk
  • Refactor out utility functions into common-lisp.utils
  • Connect Common Lisp Client to slynk transport
  • Have helper / install script in wiki page ie: a one-liner to quickstart
  • Remove swank-y code.
  • General tidy up before merging.

@Dotrar Dotrar changed the title Split out swank, lay out framework for slynk [WIP] Refactor and improve Common Lisp client Apr 27, 2022
@Olical
Copy link
Owner

Olical commented May 28, 2022

So what state would you say this is in right now? Still an improvement on what is there right now even if there's more you'd like to do? If you're kinda happy with how it behaves I'll be happy to merge and get it in the hands of users. Future changes are still of course welcome! 😄

@Olical
Copy link
Owner

Olical commented May 28, 2022

Oh actually this would be a breaking change right? Because it requires a different transport so the user would have to start their REPL differently?

@Dotrar
Copy link
Contributor Author

Dotrar commented Aug 27, 2022

closing this PR because it's messy and out of date.

changing to slynk was a lot easier than i was expecting, check out my new PR here:
#400

@Dotrar Dotrar closed this Aug 27, 2022
@Dotrar Dotrar deleted the slynk-transport branch August 27, 2022 09:06
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

Successfully merging this pull request may close these issues.

None yet

2 participants