cargo-lints 功能(https://github.com/rust-lang/cargo/pull/17298)最近稳定了。
该怎样配置这些检查，才能让它们在 CI 中和 cargo clippy -- -Dwarnings 的行为一样？
我看过 lint 参考文档(https://doc.rust-lang.org/nightly/cargo/reference/lints.html)，似乎列出了所有可用的检查，也看过解释包和工作区中 Cargo.toml 设置的清单文档(https://doc.rust-lang.org/nightly/cargo/reference/manifest.html#the-lints-section)。这两页都没有说明用哪些命令行选项把所有警告变成错误。
The cargo-lints feature (https://github.com/rust-lang/cargo/pull/17298) has recently become stable.
How should I configure these checks so they behave the same way as cargo clippy -- -Dwarnings when I run them in CI?
I've looked through the lints reference (https://doc.rust-lang.org/nightly/cargo/reference/lints.html), apparently covering every available lint, and the manifest docs (https://doc.rust-lang.org/nightly/cargo/reference/manifest.html#the-lints-section), explaining their Cargo.toml settings for packages or workspaces. Neither page explains command-line options for treating every warning as an error.
据我所知，目前还不支持。可以看这个讨论，#t-cargo > 通过命令行选项设置 Cargo lint 级别？ @ :speech_balloon: (https://rust-lang.zulipchat.com/#narrow/channel/246057-t-cargo/topic/how.20to.20allow.2Fdisable.20.20cargo.20lints.20via.20commandline.3F/near/621958684)。
As far as I know, that isn't supported yet. See this discussion: #t-cargo > setting Cargo lint levels from command-line options? @ :speech_balloon: (https://rust-lang.zulipchat.com/#narrow/channel/246057-t-cargo/topic/how.20to.20allow.2Fdisable.20.20cargo.20lints.20via.20commandline.3F/near/621958684).
留个记录，Tavin Reed 在那个讨论里推荐用 [build.warnings] 设置(https://doc.rust-lang.org/nightly/cargo/reference/config.html#buildwarnings)解决，对应的环境变量是 CARGO_BUILD_WARNINGS。
For the historcal record, Tavin Reed recommended the [build.warnings] (https://doc.rust-lang.org/nightly/cargo/reference/config.html#buildwarnings) setting (environment variable CARGO_BUILD_WARNINGS) as a solution in that discussion.
在开发环境里用 docker-compose up 启动所有服务时，我的几个容器会输出几百行又几百行内容。有没有方便的办法过滤这些输出，或者更好一些，让这些服务在 docker-compose up 运行时不要写到标准输出？
看来 D 能与 C 链接。我想用 D 编写 Python 扩展模块。我是不是漏掉了什么原因，导致这种方法根本无法运行？
python 可以这样写。 Python.withPackages (q: with q; [ fastapi ]) Micro 编辑器有类似的机制吗？ 能不能把 micro 编辑器的软件包和插件一起指定？:thinking: 那样会方便很多。
