Skip to content

Commit

Permalink
Prepare for 0.11.0 release
Browse files Browse the repository at this point in the history
  • Loading branch information
mthh committed Oct 6, 2023
1 parent eec087b commit b5607ce
Show file tree
Hide file tree
Showing 3 changed files with 17 additions and 3 deletions.
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
## Changelog

### 0.11.0 (2023-10-06)

- Add `f32` feature to use `f32` instead of `f64` for the input values and the computations (thanks to @hakolao).

### 0.10.0 (2023-03-20)

- Allow to compute isobands as `MultiPolygon` using the `isobands` method of the `ContourBuilder` struct.
Expand Down
2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "contour"
version = "0.10.0"
version = "0.11.0"
authors = ["Matthieu Viry <[email protected]>"]
edition = "2021"

Expand Down
14 changes: 12 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Add this to your `Cargo.toml`:

```toml
[dependencies]
contour = "0.10.0"
contour = "0.11.0"
```

and this to your crate root:
Expand Down Expand Up @@ -90,7 +90,7 @@ The `geojson` feature is not enabled by default, so you need to specify it in yo

```toml
[dependencies]
contour = { version = "0.10.0", features = ["geojson"] }
contour = { version = "0.11.0", features = ["geojson"] }
```

```rust
Expand Down Expand Up @@ -143,6 +143,16 @@ Feature {
}
```

**Using the `f32` feature**

By default, this crate expects `f64` values as input and uses `f64` values for its computations.
If you want to use `f32` values instead, you need to specify the `f32` feature in your `Cargo.toml`:

```toml
[dependencies]
contour = { version = "0.11.0", features = ["f32"] }
```

## WASM demo

Demo of this crate compiled to WebAssembly and used from JavaScript : [wasm_demo_contour](https://mthh.github.io/wasm_demo_contour/).
Expand Down

0 comments on commit b5607ce

Please sign in to comment.