Mike Bostock

Also, radial orientations.

Per https://github.com/d3/d3-hierarchy/issues/80#issuecomment-279228345, this is a documented limitation; the hierarchy layouts take a *root* node as input, not any *node*. To quote the README: > Before you can compute a hierarchical...

Retitled to generalize this issue.

It’s doing exactly what it’s documented to do, so I’m not sure I consider this a bug. 0 * Infinity is NaN. Why is it useful to support Infinity?

Notebook: https://observablehq.com/d/87334a0278f99fe5

I think what we’re missing, as well, is a d3.interpolateLinearRgb that is the equivalent of [color-interpolation: linearRGB](https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/color-interpolation) in CSS (see [color conversion sample code](https://www.w3.org/TR/css-color-4/#color-conversion-code)). I’m not sure we should change...

I’ve reproduced this here: https://bl.ocks.org/mbostock/98edae5ce16c3400b5bcd180653a3717 The way transform interpolation currently works is that it decomposes the start and end transform into a standard matrix representation, and then uses the [CSS...

Are you imagining something like d3.interpolateMeta(_a_, _b_) that takes two interpolators and returns an interpolator that linearly interpolates the output of _a_ and _b_?

I was thinking this: ``` js function interpolateMeta(a, b) { return (t) => interpolate(a(t), b(t))(t); } ``` Which, as you point out, isn’t ideal from a performance perspective because it...

Oh also, as far as the dynamically-typed nature of d3.interpolate goes, the behavior of d3.interpolateMeta could be defined such that the first time the returned interpolator is invoked, it determines...