summaryrefslogtreecommitdiffstats
path: root/vendor/plotters/src/chart
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-06-19 09:26:03 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-06-19 09:26:03 +0000
commit9918693037dce8aa4bb6f08741b6812923486c18 (patch)
tree21d2b40bec7e6a7ea664acee056eb3d08e15a1cf /vendor/plotters/src/chart
parentReleasing progress-linux version 1.75.0+dfsg1-5~progress7.99u1. (diff)
downloadrustc-9918693037dce8aa4bb6f08741b6812923486c18.tar.xz
rustc-9918693037dce8aa4bb6f08741b6812923486c18.zip
Merging upstream version 1.76.0+dfsg1.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'vendor/plotters/src/chart')
-rw-r--r--vendor/plotters/src/chart/context/cartesian2d/draw_impl.rs5
-rw-r--r--vendor/plotters/src/chart/dual_coord.rs2
-rw-r--r--vendor/plotters/src/chart/series.rs4
3 files changed, 3 insertions, 8 deletions
diff --git a/vendor/plotters/src/chart/context/cartesian2d/draw_impl.rs b/vendor/plotters/src/chart/context/cartesian2d/draw_impl.rs
index 6dafa0879..174527378 100644
--- a/vendor/plotters/src/chart/context/cartesian2d/draw_impl.rs
+++ b/vendor/plotters/src/chart/context/cartesian2d/draw_impl.rs
@@ -119,10 +119,7 @@ impl<'a, DB: DrawingBackend, X: Ranged, Y: Ranged> ChartContext<'a, DB, Cartesia
y1 = axis_range.end;
}
- area.draw(&PathElement::new(
- vec![(x0, y0), (x1, y1)],
- *axis_style,
- ))?;
+ area.draw(&PathElement::new(vec![(x0, y0), (x1, y1)], *axis_style))?;
}
Ok(axis_range)
diff --git a/vendor/plotters/src/chart/dual_coord.rs b/vendor/plotters/src/chart/dual_coord.rs
index d5960e030..434e34776 100644
--- a/vendor/plotters/src/chart/dual_coord.rs
+++ b/vendor/plotters/src/chart/dual_coord.rs
@@ -20,7 +20,7 @@ use plotters_backend::{BackendCoord, DrawingBackend};
/// This situation is quite common, for example, we with two different coodinate system.
/// For instance this example <img src="https://plotters-rs.github.io/plotters-doc-data/twoscale.png"></img>
/// This is done by attaching a second coordinate system to ChartContext by method [ChartContext::set_secondary_coord](struct.ChartContext.html#method.set_secondary_coord).
-/// For instance of dual coordinate charts, see [this example](https://github.com/38/plotters/blob/master/examples/two-scales.rs#L15).
+/// For instance of dual coordinate charts, see [this example](https://github.com/plotters-rs/plotters/blob/master/examples/two-scales.rs#L15).
/// Note: `DualCoordChartContext` is always deref to the chart context.
/// - If you want to configure the secondary axis, method [DualCoordChartContext::configure_secondary_axes](struct.DualCoordChartContext.html#method.configure_secondary_axes)
/// - If you want to draw a series using secondary coordinate system, use [DualCoordChartContext::draw_secondary_series](struct.DualCoordChartContext.html#method.draw_secondary_series). And method [ChartContext::draw_series](struct.ChartContext.html#method.draw_series) will always use primary coordinate spec.
diff --git a/vendor/plotters/src/chart/series.rs b/vendor/plotters/src/chart/series.rs
index 8c430cbef..4aecf6a1f 100644
--- a/vendor/plotters/src/chart/series.rs
+++ b/vendor/plotters/src/chart/series.rs
@@ -250,9 +250,7 @@ impl<'a, 'b, DB: DrawingBackend + 'a, CT: CoordTranslate> SeriesLabelStyle<'a, '
continue;
}
- funcs.push(
- draw_func.unwrap_or(&|p: BackendCoord| EmptyElement::at(p).into_dyn()),
- );
+ funcs.push(draw_func.unwrap_or(&|p: BackendCoord| EmptyElement::at(p).into_dyn()));
label_element.push_line(label_text);
}