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

Temporary fix for #109 #113

Merged
merged 1 commit into from Aug 4, 2015
Merged

Conversation

conklech
Copy link
Contributor

@conklech conklech commented Aug 3, 2015

This implements @HeinrichApfelmus's suggested fix to #109.

Could we get this up on Hackage?

@HeinrichApfelmus
Copy link
Owner

Ok, let's push the temporary fix to Hackage. Thanks!

HeinrichApfelmus added a commit that referenced this pull request Aug 4, 2015
@HeinrichApfelmus HeinrichApfelmus merged commit 98aea34 into HeinrichApfelmus:master Aug 4, 2015
HeinrichApfelmus added a commit that referenced this pull request Aug 10, 2015
The children and the event handlers associated to an ‘Element’
are now managed by two separate ‘RemotePtr’.

Previously, both the children of an ‘Element’ and the event handlers
associated to this element where “attached” to it
by using ‘Foreign.addReachable’. Clearing all child elements
had the nasty side effect of removing the event handlers as well.

Now, we can use ‘Foreign.clearReachable’ on the ‘elChildren’
pointer to sever the connection to the child elements,
allowing them to be garbage collected if there is no reference to them
on the server side anymore.

Fix #109, #113
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