A game's code is supposed to have its own error type (that can wrap over ggez::GameError) but you are forced to unwrap/expect all your errors in EventHandler's draw and update methods (because you can't turn them into GameError), right? Is this documented somewhere?

Related to ggez/ggez#421

There's no mention of highlighted_html_for_string usage in the examples, or anywhere I've found outside the API docs. There's an example of highlighted_html_for_file, but this doesn't require a SyntaxReference param, which there's no example of either.

Can you provide an example or docs for extending a Qt class? E.g. A simple example that extends qt_widgets::main_window::MainWindow and overrides closeEvent? This is commonly needed to intercept closing of a window.

(I assume this is not implemented per rust-qt/ritual#26, I'll just leave this open because a simp

I would be neat if you could specify a max width for columns and/or tables and have prettytable automatically truncate strings (and probably add a configurable indicator like ...) that exceed that length.

When adding a license exception, you must enumerate each allowed license needed to satisfy the expression for the crate, even ones that are already allowed globally. Instead, the allowed list should just be additive to any existing global license setting.

See #119

Just a advise, like:

https://github.com/servo/rust-url/blob/28314752bf138a87bd8151f610d385629dec5710/Cargo.toml#L43

There is no [features] section in Cargo.toml, but serde is a feature of url, I can use it in my Cargo.toml:

url = { version = "2.1.1", features = ["serde"] }

So should this optional dependency show in Feature flags?

This should work:

cat test.txt | unic-inspector

This is a tracking issue for additional Indexer implementations.

Here is a non-exhaustive list of potential candidates for an Indexer implementation:

• RemoteIndex:
  Requires to implement a companion server.
  The idea is to have a clone of the index on another machine on which a companion server is running, you would then point Alexandrie to that server and it would take care o

As nice as it is to be able to remove the blatantly bad stuff, sometimes you don't want the user to be able to enter any HTML at all. You could do this by escaping the markup, but if having a database with < in it doesn't appeal to you, or you're worried about double-escaping or similarly nasty accidents, you could use a function that just tells you if a string has any HTML tags in it. And in

In the documentation for server::Multipart::foreach_iterator, you use an internal iterator due to Rust's iterators not supporting elements that borrow from the iterator. There is a streaming-iterator crate with a [StreamingIterator](https://docs.rs/stre

Pleco has a ton of features and customization. However, it's not very clear on how to actually incorporate the crate inside of a project.

The Wiki needs to be updated to include at least:

1. Basic operation and creating boards
2. Functions available to the board, and when to use each
3. How to generate moves from the board

See the official cargo layout. Keep in mind that only integrations tests should go to tests/ and not the unit tests.

Inflector is different from most crates in using a capital letter to start it's crate name. It would be nice if it was consistent with the rest of the ecosystem.