@birdsarah particularly interested what you think of line_stack API. Currently have

line_stack(x, y, **kw)

which expects one of x or y to be sequence to "stack", but not both (will error if both are). Alternatively could do

line_stack(stackers, **kw)

which would explicitly have one arg for the stackers, and whether it is x or y depends on the the other one being provided as a kw arg, e.g line_stack([...], x=...) will stack y coords, because x= was provided.

Other option is to explicitly have hline_stack and vline_stack but that's getting a but verbose even for me.

Sorry I didn't see your message in time. Here's my thoughts anyway.....don't hate me....but I actually like hline_stack, vline_stack. My reasoning is that it is in keeping with an existing mental model for hbar, vbar, harea, varea... I think it's good to follow patterns whenever they're available. My take is that verbose is annoying, but not as annoying as having to look up syntax.

FYI I have a WIP branch that makes that change

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.