Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixup unary_union docs #1286

Merged
merged 2 commits into from
Dec 19, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/workflows/test.yml
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@ jobs:
- geo_postgis
- geo_fuzz
- bench
- docs
if: success()
steps:
- name: Mark the job as a success
Expand Down
4 changes: 2 additions & 2 deletions geo/src/algorithm/bool_ops/mod.rs
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ use i_overlay::string::clip::ClipRule;
///
/// # Performance
///
/// For union operations on a large number of [`Polygon`]s or [`MultiPolygons`],
/// For union operations on a large number of [`Polygon`]s or [`MultiPolygon`]s,
/// using [`unary_union`] will yield far better performance.
pub trait BooleanOps {
type Scalar: BoolOpsNum;
Expand Down Expand Up @@ -129,7 +129,7 @@ pub enum OpType {
/// This is typically much faster than `union`ing a bunch of geometries together one at a time.
///
/// Note: Geometries can be wound in either direction, but the winding order must be consistent,
/// and the polygon's interiors must be wound opposite to its exterior.
/// and each polygon's interior rings must be wound opposite to its exterior.
///
/// See [Orient] for more information.
///
Expand Down
Loading