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

Make keys generic over version cont'd #31

Merged
merged 3 commits into from
Oct 21, 2021
Merged

Make keys generic over version cont'd #31

merged 3 commits into from
Oct 21, 2021

Conversation

brycx
Copy link
Owner

@brycx brycx commented Oct 21, 2021

There were some ref issues preventing me from pushing to upstream, so I made a new PR just since it was quicker.

Replacement of #25 (where discussion is located)

not-my-profile and others added 3 commits October 21, 2021 19:51
Turns version mismatch errors from runtime errors into compile-time
errors, giving us compile-time algorithm lucidity.
@brycx brycx merged commit 1eb2e03 into master Oct 21, 2021
@brycx brycx deleted the generic-vers branch October 21, 2021 18:04
@not-my-profile
Copy link
Contributor

not-my-profile commented Oct 21, 2021

Thanks :) Just FYI for the future I prefer my commits to be merged unsquashed, so that it's clear who made which changes (e.g. for git blame).

@brycx
Copy link
Owner Author

brycx commented Oct 21, 2021

Just FYI for the future I prefer my commits to be merged unsquashed, so that it's clear who made which changes (e.g. for git blame).

Thanks for letting me know. I generally prefer squashed to keep the git log clean, but I'll try to keep this in mind as much as possible. If a PR collects too many commits however, then I might opt for squashing regardless.

@not-my-profile
Copy link
Contributor

I have nothing against squashing per se. I just don't like squashing commits from different authors together. Note that with git rebase -i you can easily squash only specific commits (by fixing them up).

@brycx
Copy link
Owner Author

brycx commented Oct 21, 2021

I'll look into git rebase -i and keep the different authors point in mind. I get how you mean squashing probably wasn't the best choice for this PR.

@not-my-profile
Copy link
Contributor

I love interactive rebases^^ it lets you easily rearrange commits, reword specific commit messages, edit specific commits etc.

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