Skip to content

Commit 0f261de

Browse files
authored
Merge pull request #42 from EliahKagan/update-doc-next
Really don't describe `progress-tree-log` as a default feature
2 parents cf70e4a + 901359a commit 0f261de

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ This crate comes with various cargo features to tailor it to your needs.
2323
* **progress-tree-hp-hashmap** - high-performance registry for pregree tree nodes in case of ultra-heavy insertions and deletions.
2424
* If this is necessary, it's probably impossible to resonably visualize the progress tree anyway, but the option exists nonetheless in case
2525
it is ever needed. Historically, this was the default, but now it seems simpler is better and just fine for typical programs.
26-
* **progress-tree-log** _(default)_
26+
* **progress-tree-log**
2727
* If logging in the `log` crate is initialized, a `log` will be used to output all messages provided to
2828
`tree::Item::message(…)` and friends. No actual progress is written.
2929
* May interfere with `render-tui` or `render-line`, or any renderer outputting to the console.

0 commit comments

Comments
 (0)