slang.git/tests/language-feature/capability/capabilitySimplification2.slang, branch masterMaking it easier to work with shadershttps://git.yummers.dev/slang.git/atom?h=master2025-06-30T21:32:50+00:00Add MLP training examples. (#7550)2025-06-30T21:32:50+00:00Yong Heyonghe@outlook.com2025-06-30T21:32:50+00:00urn:sha1:f28f67d988158d6c46f7ffe967152f98d32a37b2
* Add MLP training examples.
* Formatting fix.
* Fix.
* Improve documentation on coopvector.
* Improve doc.
* Update doc.
* Fix typo.
* Cleanup shader.
* Cleanup.
* Fix test.
* Fix type check recursion.
* Fix.
* Fix.
* Fix override check.Simplify `CapabilitySet` Diagnostic Printing (#4678)2024-07-23T13:36:38+00:00ArielG-NV159081215+ArielG-NV@users.noreply.github.com2024-07-23T13:36:38+00:00urn:sha1:509bfd8bbaaf021507c4045b5fd9eaf43276dc0a
Fixes: #4675
Fixes: #4683
Fixes: #4443
Fixes: #4585
Fixes: #4172
Made the following changes:
1. All capability diagnostic printing logic tries to simplify before printing. This means that we do not print atoms which imply another atom.
2. Do not print the `_` prefix part of atom names since it is misleading users on what they should use to solve a capability issue encountered. (`_Internal` `External` atom changes are not in this PR)
3. Bundle together printing of all sets which contain exactly the same atoms (excluding abstract atoms). This allows printing the following `vertex/fragment/hull/domain/... + glsl` instead of `vertex + glsl | fragment + glsl | hull + glsl | domain + glsl | ....`
4. Rework how entry-point errors are reported to users (example at bottom of PR comment)
5. Rework how atom-provenance data is collected to be leaner and more useful so we can rework the errors. There are 2 notable changes here:
* We no longer store a list which describes where the first of an `CapabilityAtom` comes from. This heavily simplifies AST logic for the capability system. AST parsing of capabilities is much faster. The trade-off is faster AST parsing and correct AST node data for slower diagnostics if an error is found
* atom-provenance data now stores a reference to an atom's use-site to provide information on **where** and **what** is wrong with user code versus only sharing **what** and not where.