Skip to content

Conversation

@plantpurecode
Copy link

This is our attempt at a fix for #260. We verified that this doesn't break any existing tests, but we haven't tested all potential scenarios where this could alter existing, untested behavior.

@wearhere
Copy link
Contributor

wearhere commented Sep 3, 2014

Can you squash this into a single "good" commit so that we have a clean commit history? Otherwise looks good. Re:

we haven't tested all potential scenarios where this could alter existing, untested behavior.

I don't know if that'd even be possible. :D The only behavior we do (indeed, can) guarantee is that which is tested; we'll handle additional issues as they're reported. But thank you for thinking about it--there are obviously different ways to fix things and we'd like to take fixes that are as conservative as possible to avoid potential issues down the line.

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.

2 participants