-
Notifications
You must be signed in to change notification settings - Fork 246
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.
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
Capability System: Redesign how failed capability providence is described to a user #4172
Labels
goal:quality & productivity
Quality issues and issues that impact our productivity coding day to day inside slang
kind:enhancement
a desirable new feature, option, or behavior
Comments
ArielG-NV
changed the title
Capability
Capability System: Redesign how failed capabilities on EntryPoints are managed
May 15, 2024
ArielG-NV
changed the title
Capability System: Redesign how failed capabilities on EntryPoints are managed
Capability System: Redesign how failed capabilities on EntryPoints are described to a user
May 15, 2024
ArielG-NV
added
kind:enhancement
a desirable new feature, option, or behavior
goal:quality & productivity
Quality issues and issues that impact our productivity coding day to day inside slang
labels
May 15, 2024
ArielG-NV
changed the title
Capability System: Redesign how failed capabilities on EntryPoints are described to a user
Capability System: Redesign how failed capabilities on EntryPoints<->compileTarget are described to a user
May 15, 2024
ArielG-NV
changed the title
Capability System: Redesign how failed capabilities on EntryPoints<->compileTarget are described to a user
Capability System: Redesign how failed capability providence is described to a user
Jul 18, 2024
example of why this needs fixing (notice the repeat of errors):
|
I think this issue needs a "repro steps". |
Repro: #4443 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
goal:quality & productivity
Quality issues and issues that impact our productivity coding day to day inside slang
kind:enhancement
a desirable new feature, option, or behavior
Currently in the capabilities system, erroring once we reach a stage of checking EntryPoints<->compileTarget (Diagnostics::entryPointUsesUnavailableCapability) produces assumptions of what went wrong.
These assumptions assumes based on providence of a single Decl that any incompatible capability may be the problem. This erroring works well when the problem is straight-forward or the function has little capabilities defined. When the problem is within a function with many overlapping capabilities the current "providence" tracking provides little assistance in erroring due to only tracking a single "providence".
One solution to this would be to redesign the approach to store UIntSets of
callee
andparent
functions that remove a targetThe text was updated successfully, but these errors were encountered: