Ensure that niced domains always span ticks#210
Conversation
|
Now the question is there any situation we aren’t anticipating that will go into an infinite loop. :) |
|
Or instead perhaps a reasonable |
|
We could attempt to prove that this specific code will always halt but better be safe. I added a commit to limit the number of iterations with |
|
I think my preference is to prove that it will always halt, but that requires more mental effort. :) |
|
Ideally, we would prove it for all future versions of the code as well. |
|
Everyone please be considerate. The |
|
@mbostock I'm happy with the code. Is there anything you want me to change? |
|
@mbostock could you include this patch in a release? |
curran
left a comment
There was a problem hiding this comment.
The logic appears sound. The incidental var --> const/let changes will make the codebase internally inconsistent. Maybe use var everywhere? I'm all for ES6 migration, but maybe that would be best to do on all modules at once, as a separate PR.
|
I went back to var and will send a separate pull request switching to let/const. |
|
I sent #212 |
|
yes I think so—we're currently preparing a rather big release (ie d3v6) |
|
🎉 Awesome. Looking forward to it. |
fixes #209