Repository: diesel-rs/diesel
File: diesel/src/lib.rs (Rust)

Code before:
//! [discussion]: https://github.com/diesel-rs/diesel/discussions/categories/q-a
//!
//! # Crate feature flags
//!
//! The following feature flags are considered to be part of diesels public
//! API. Any feature flag that is not listed here is **not** considered to
//! be part of the public API and can disappear at any point in time:

//!
//! - `sqlite`: This feature enables the diesel sqlite backend. Enabling this feature requires per default
//!   a compatible copy of `libsqlite3` for your target architecture. Alternatively, you can add `libsqlite3-sys`
//!   with the `bundled` feature as a dependency to your crate so SQLite will be bundled:
//!   ```toml
//!   [dependencies]
//!   libsqlite3-sys = { version = "0.29", features = ["bundled"] }
//!   ```
//! - `postgres`: This feature enables the diesel postgres backend. This features implies `postgres_backend`
//!   Enabling this feature requires a compatible copy of `libpq` for your target architecture.
//!   Alternatively, you can add `pq-sys` with the `bundled` feature as a dependency to your
//!   crate so libpq will be bundled:
//!   ```toml
//!   [dependencies]
//!   pq-sys = { version = "0.6", features = ["bundled"] }
//!   openssl-sys = { version = "0.9.100", features = ["vendored"] }
//!   ```
//! - `mysql`: This feature enables the idesel mysql backend. This feature implies `mysql_backend`.
//!   Enabling this feature requires a compatible copy of `libmysqlclient` for your target architecture.
//!   Alternatively, you can add `mysqlclient-sys` with the `bundled` feature as a dependency to your
//!   crate so libmysqlclient will be bundled:
//!   ```toml
//!   [dependencies]
//!   mysqlclient-sys = { version = "0.4", features = ["bundled"] }
//! - `postgres_backend`: This feature enables those parts of diesels postgres backend, that are not dependent
//!   on `libpq`. Diesel does not provide any connection implementation with only this feature enabled.
//!   This feature can be used to implement a custom implementation of diesels `Connection` trait for the
//!   postgres backend outside of diesel itself, while reusing the existing query dsl extensions for the
//!   postgres backend
//! - `mysql_backend`: This feature enables those parts of diesels mysql backend, that are not dependent
//!   on `libmysqlclient`. Diesel does not provide any connection implementation with only this feature enabled.
//!   This feature can be used to implement a custom implementation of diesels `Connection` trait for the
//!   mysql backend outside of diesel itself, while reusing the existing query dsl extensions for the
//!   mysql backend
//! - `returning_clauses_for_sqlite_3_35`: This feature enables support for `RETURNING` clauses in the sqlite backend.
//!   Enabling this feature requires sqlite 3.35.0 or newer.
//! - `32-column-tables`: This feature enables support for tables with up to 32 columns.
//!   This feature is enabled by default. Consider disabling this feature if you write a library crate
//!   providing general extensions for diesel or if you do not need to support tables with more than 16 columns
//!   and you want to minimize your compile times.
//! - `64-column-tables`: This feature enables support for tables with up to 64 columns. It implies the
//!   `32-column-tables` feature. Enabling this feature will increase your compile times.
//! - `128-column-tables`: This feature enables support for tables with up to 128 columns. It implies the

Review comment (suggestion):
Misprint
```suggestion
//! - `mysql`: This feature enables the diesel mysql backend. This feature implies `mysql_backend`.
```

Code after:
//! [discussion]: https://github.com/diesel-rs/diesel/discussions/categories/q-a
//!
//! # Crate feature flags
//!
//! The following feature flags are considered to be part of diesels public
//! API. Any feature flag that is not listed here is **not** considered to
//! be part of the public API and can disappear at any point in time:

//!
//! - `sqlite`: This feature enables the diesel sqlite backend. Enabling this feature requires per default
//!   a compatible copy of `libsqlite3` for your target architecture. Alternatively, you can add `libsqlite3-sys`
//!   with the `bundled` feature as a dependency to your crate so SQLite will be bundled:
//!   ```toml
//!   [dependencies]
//!   libsqlite3-sys = { version = "0.29", features = ["bundled"] }
//!   ```
//! - `postgres`: This feature enables the diesel postgres backend. This features implies `postgres_backend`
//!   Enabling this feature requires a compatible copy of `libpq` for your target architecture.
//!   Alternatively, you can add `pq-sys` with the `bundled` feature as a dependency to your
//!   crate so libpq will be bundled:
//!   ```toml
//!   [dependencies]
//!   pq-sys = { version = "0.6", features = ["bundled"] }
//!   openssl-sys = { version = "0.9.100", features = ["vendored"] }
//!   ```
//! - `mysql`: This feature enables the diesel mysql backend. This feature implies `mysql_backend`.
//!   Enabling this feature requires a compatible copy of `libmysqlclient` for your target architecture.
//!   Alternatively, you can add `mysqlclient-sys` with the `bundled` feature as a dependency to your
//!   crate so libmysqlclient will be bundled:
//!   ```toml
//!   [dependencies]
//!   mysqlclient-sys = { version = "0.4", features = ["bundled"] }
//! - `postgres_backend`: This feature enables those parts of diesels postgres backend, that are not dependent
//!   on `libpq`. Diesel does not provide any connection implementation with only this feature enabled.
//!   This feature can be used to implement a custom implementation of diesels `Connection` trait for the
//!   postgres backend outside of diesel itself, while reusing the existing query dsl extensions for the
//!   postgres backend
//! - `mysql_backend`: This feature enables those parts of diesels mysql backend, that are not dependent
//!   on `libmysqlclient`. Diesel does not provide any connection implementation with only this feature enabled.
//!   This feature can be used to implement a custom implementation of diesels `Connection` trait for the
//!   mysql backend outside of diesel itself, while reusing the existing query dsl extensions for the
//!   mysql backend
//! - `returning_clauses_for_sqlite_3_35`: This feature enables support for `RETURNING` clauses in the sqlite backend.
//!   Enabling this feature requires sqlite 3.35.0 or newer.
//! - `32-column-tables`: This feature enables support for tables with up to 32 columns.
//!   This feature is enabled by default. Consider disabling this feature if you write a library crate
//!   providing general extensions for diesel or if you do not need to support tables with more than 16 columns
//!   and you want to minimize your compile times.
//! - `64-column-tables`: This feature enables support for tables with up to 64 columns. It implies the
//!   `32-column-tables` feature. Enabling this feature will increase your compile times.
//! - `128-column-tables`: This feature enables support for tables with up to 128 columns. It implies the