Skip to content

Improve trace-ability of errors in stdlib fns#15

Closed
StachuDotNet wants to merge 2 commits into
mainfrom
reduce-sourcenone-usage
Closed

Improve trace-ability of errors in stdlib fns#15
StachuDotNet wants to merge 2 commits into
mainfrom
reduce-sourcenone-usage

Conversation

@StachuDotNet

@StachuDotNet StachuDotNet commented Jan 4, 2023

Copy link
Copy Markdown
Owner

Changelog:

Editor
- improve trace-ability of errors that occur in stdlib fns

Increase our accuracy, frequency, and precision in which we 'blame' errors, by replacing SourceNone usages with the IDs of code that caused the errors originally.

keeping this PR in my fork until it's useful

it'd also be worth reviewing the DErrors that do have ids - consider whether the ID assigned as the issue is truly the best ID.

@StachuDotNet StachuDotNet changed the title Mark SourceNone usages that are worth reducing/exploring Improve trace-ability of errors in stdlib fns Jan 4, 2023
StachuDotNet added a commit that referenced this pull request Mar 1, 2023
Slightly improve VSCode extension 'executor' loading; add commentary
@StachuDotNet
StachuDotNet deleted the reduce-sourcenone-usage branch June 9, 2023 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant