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

fixes problem with MutableMap's setValue #190

Merged
merged 1 commit into from
Oct 5, 2022
Merged

fixes problem with MutableMap's setValue #190

merged 1 commit into from
Oct 5, 2022

Conversation

hugobrancowb
Copy link
Contributor

As Dart's only way to reference an object is using itself, My suggestion is to pass DartMutableMap to all entries so it can be changed the proper way.

Closes #55

as described in issue #55

Signed-off-by: Hugo Branco <[email protected]>
@passsy
Copy link
Owner

passsy commented Oct 5, 2022

You Rock

@passsy passsy merged commit 80402d4 into passsy:master Oct 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

KMutableEntry.setValue doesn't change value in collection
2 participants