break!: merge Tokenizer::new_with_emitter into Tokenizer::new

The Tokenizer does not perform any state switching, since
proper state switching requires a feedback loop between
tokenization and DOM tree building. Using the Tokenizer
directly therefore is a bit of a pitfall, since you might
not expect it to e.g. tokenize `<script><b>` as:

    StartTag(StartTag { name: "script", .. })
    StartTag(StartTag { name: "b", .. })

Since we don't want to make walking into pitfalls
particularly easy, this commit changes the Tokenizer::new
method so that you have to specify the Emitter.
Since this makes new_with_emitter redundant it is removed.

1 files changed, 9 insertions, 2 deletions

diff --git a/examples/tokenize.rs b/examples/tokenize.rs
index ceb5751..5776362 100644
--- a/examples/tokenize.rs
+++ b/examples/tokenize.rs
@@ -1,9 +1,16 @@
 //! Let's you easily try out the tokenizer with e.g.
 //! printf '<h1>Hello world!</h1>' | cargo run --example=tokenize
-use html5tokenizer::{BufReadReader, Tokenizer};
+
+use html5tokenizer::{DefaultEmitter, Tokenizer};
+use std::io::BufReader;
 
 fn main() {
-    for token in Tokenizer::new(BufReadReader::new(std::io::stdin().lock())).flatten() {
+    for token in Tokenizer::new(
+        BufReader::new(std::io::stdin().lock()),
+        DefaultEmitter::<_, ()>::default(),
+    )
+    .flatten()
+    {
         println!("{:?}", token);
     }
 }