Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

date-check: crates-io #1425

Merged
merged 1 commit into from
Aug 11, 2022
Merged

date-check: crates-io #1425

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions src/crates-io.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,20 +1,20 @@
# crates.io Dependencies

The Rust compiler supports building with some dependencies from `crates.io`.
For example, `log` and `env_logger` come from `crates.io`.
Examples are `log` and `env_logger`.

In general, you should avoid adding dependencies to the compiler for several
reasons:
In general,
you should avoid adding dependencies to the compiler for several reasons:

- The dependency may not be high quality or well-maintained, whereas we want
the compiler to be high-quality.
- The dependency may not be of high quality or well-maintained.
- The dependency may not be using a compatible license.
- The dependency may have transitive dependencies that have one of the above
problems.

As of <!-- date-check --> February 2022, there is no official policy for vetting
new dependencies to the compiler. Generally, new dependencies are not added
to the compiler unless there is a good reason to do so.
As of <!-- date-check --> Aug 2022,
there is no official policy for vetting new dependencies to the compiler.
Decisions are made on a case-by-case basis,
during code review.

## Permitted dependencies

Expand Down