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

Bring mutating optimisations back #13

Closed
wants to merge 8 commits into from
Closed

Bring mutating optimisations back #13

wants to merge 8 commits into from

Conversation

DhairyaLGandhi
Copy link
Member

No description provided.

@DhairyaLGandhi DhairyaLGandhi changed the title :Q Bring mutating optimisations back Feb 13, 2021
@DhairyaLGandhi DhairyaLGandhi reopened this Mar 8, 2021
Copy link
Member

@darsnack darsnack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some typos

Co-authored-by: Kyle Daruwalla <daruwalla.k.public@icloud.com>
Copy link
Member

@darsnack darsnack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple more typos restructuring the state tuple

Co-authored-by: Kyle Daruwalla <daruwalla.k.public@icloud.com>
@darsnack
Copy link
Member

@DhairyaLGandhi I have rebased this locally, do you mind if I push it?

@DhairyaLGandhi
Copy link
Member Author

I think I wanted to handle this separately. It also seems like some other changes were merged hastily?

@darsnack
Copy link
Member

What do you mean handled separately? This has been in need of a rebase for months (any recent changes weren't the reason for preventing this from being merged).

@DhairyaLGandhi
Copy link
Member Author

Mutation isn't the goal - so Handling the code duplication separately. Mutation should not be the default unless it is absolutely needed. The api change also needs to be accounted for.

@darsnack
Copy link
Member

I am confused. Do you still want to merge this PR or not? All I want is to merge this PR.

@DhairyaLGandhi
Copy link
Member Author

We can merge it when we need it. We'd prolly not make mutation the default though.

@darsnack
Copy link
Member

Superseded by #31.

@darsnack darsnack closed this Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

2 participants