Version 1.0#5
Open
phoe wants to merge 1 commit into
Open
Conversation
phoe
force-pushed
the
master
branch
2 times, most recently
from
13933a0 to
b316f1a
Compare
Author
|
Beep boop. |
Author
|
Beep beep boop. Should I request Quicklisp to pull from my tree? |
Author
|
OK, done. I volunteer to maintain the fork. |
Owner
|
I'm sorry phone, I haven't been in the right headspace to lisp for while. I agree you taking over is the best move. I'll comment to that effect on the quicklisp thread |
Author
|
OK, thanks! I'll take over then. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1
Closes #2
Closes #3
Closes #4
I kinda decided to rewrite the source code from scratch, make it configurable in a few ways, handle circular data structures, generously add comments, and give it some proper tests and documentation. All while mostly maintaining backwards compatibility (I hope no one depends on this library in a way that requires the behavior to be exactly the same).
I volunteer to co-maintain this library since I know all of its code now.
What do you think? Is this mergeable?