69ff673feb
WebGPU CTS run: https://treeherder.mozilla.org/jobs?repo=try&revision=02e0b7243aedb87972250504dd6bf64d74ff3f96 I updated the patch with the expectations from that run. There were some regressions in tier 2: - `testing/web-platform/mozilla/meta/webgpu/cts/webgpu/shader/execution/expression/call/builtin/textureStore/cts.https.html.ini` - test path: `webgpu:shader,execution,expression,call,builtin,textureStore:bgra8unorm_swizzle:*` - with error: "Error: Unexpected validation error occurred: Shader module creation failed: Parsing error" - see: https://treeherder.mozilla.org/logviewer?job_id=496834446&repo=try&lineNumber=3089 - `testing/web-platform/mozilla/meta/webgpu/cts/webgpu/shader/validation/expression/call/builtin/value_constructor/cts.https.html.ini` - new failures related to vector/matrix constructors with abstract types - see: https://treeherder.mozilla.org/logviewer?job_id=496835790&repo=try&lineNumber=2094 There were also a new failures in tier 3 related to abstract types: - `testing/web-platform/mozilla/meta/webgpu/cts/webgpu/shader/validation/expression/binary/and_or_xor/cts.https.html.ini` - `testing/web-platform/mozilla/meta/webgpu/cts/webgpu/shader/validation/expression/binary/bitwise_shift/cts.https.html.ini` - `testing/web-platform/mozilla/meta/webgpu/cts/webgpu/shader/validation/expression/binary/comparison/cts.https.html.ini` - `testing/web-platform/mozilla/meta/webgpu/cts/webgpu/shader/validation/expression/binary/div_rem/cts.https.html.ini` Overall, there were lots of new passes related to abstract types and I suspect those new failures were actually false positives previously. Limit tests at `testing/web-platform/mozilla/meta/webgpu/cts/webgpu/api/validation/capability_checks/limits/` are as noisy as always... One more try push with all the changes: https://treeherder.mozilla.org/jobs?repo=try&revision=e3b4d3b039ca9e84aa2f4ec0b824c4530f41695d Differential Revision: https://phabricator.services.mozilla.com/D239942
Document your crate's feature flags
This crate provides a macro that extracts documentation comments from Cargo.toml
To use this crate, add #![doc = document_features::document_features!()] in your crate documentation.
The document_features!() macro reads your Cargo.toml file, extracts feature comments and generates
a markdown string for your documentation.
Use ## and #! comments in your Cargo.toml to document features, for example:
[dependencies]
document-features = "0.2"
## ...
[features]
## The foo feature enables the `foo` functions
foo = []
## The bar feature enables the [`bar`] module
bar = []
#! ### Experimental features
#! The following features are experimental
## Activate the fusion reactor
fusion = []
These comments keep the feature definition and documentation next to each other, and they are then rendered into your crate documentation.
Check out the documentation for more details.
Contributions
Contributions are welcome. We accept pull requests and bug reports.
License
MIT OR Apache-2.0