@emilk Thanks for the review! I'm very much open to having a separate Points primitive, in fact I was going to take this approach first. But everything is very much built around Curve right now and introducing a separate Points struct would lead to a lot of duplicate code. Maybe we could unite them in a Series primitive which has a field that defines whether it's a curve or a set of points? Maybe you have an idea?

@emilk I've now created a separate Points primitive, let me know what you think. It has lead to some duplicate code but made other parts much cleaner and straight forward. Both Curves and Points now have just one constructor, which takes a ValuesSeries object, like so:

let curve = Curve::new(ValueSeries::from_values_iter(sin));
let points = Points::new(ValueSeries::from_values_iter(sin));
ui.add(
    Plot::new("Test Plot").curve(curve).points(points)
);

One issue with this approach (apart from the duplicate code) is that points are always drawn on top of curves. But I want the user to have full control over the drawing order. One way to fix both issues might be to share an interface between Points and Curve and then store them in a vector of boxes. I can give that a shot...

Done, I'm quite happy with how this turned out. I also took the chance to rename Curve to Line since it's more general and we're breaking a lot here anyways.

@emilk Thanks for having another look. Much appreciated. I applied all your suggestions.