-
Notifications
You must be signed in to change notification settings - Fork 23
more Base lenses #69
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
more Base lenses #69
Conversation
c06b711 to
a57cb70
Compare
|
Could you force-push less, please? Doing so makes Github loose track of history and comments... |
|
Interesting, I've always thought it's best to keep the commit history clean, without back and forth changes. That's why I tend to edit existing commits instead of creating new ones, to keep change history linear. |
|
I think the better way to achieve that are rebasing or squashing at the end. But I'm by no means a Git guru, just noticed that Github doesn't properly keep track of comment history and links with force pushes. It's not a big deal though. |
|
I also think there are some tradeoffs with github between nice looking git history and incremental reviewability. Personally, I prefer better reviewability. |
|
Anyway, is there anything else left regarding changes to this PR? |
jw3126
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks these are nice additions especially fixing slice indexing!
No description provided.