You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2020. It is now read-only.
Good warnings and error reporting are of great help to tool developers or general developers alike.
The warning system should not be a burden in environments where warnings are undesired/unactionable - it should get out of the way without impacting perf. At the same time we want the warning system be flexible enough to enable PEVerify-like scenarios (dotnet/coreclr/#295) for the type system in the future.
The error system should be based on standardized exceptions that provide context with programmatic access (e.g. having an object-typed Pertinent property that points to a type system object associated with the exception).
The text was updated successfully, but these errors were encountered:
Good warnings and error reporting are of great help to tool developers or general developers alike.
The warning system should not be a burden in environments where warnings are undesired/unactionable - it should get out of the way without impacting perf. At the same time we want the warning system be flexible enough to enable PEVerify-like scenarios (dotnet/coreclr/#295) for the type system in the future.
The error system should be based on standardized exceptions that provide context with programmatic access (e.g. having an object-typed Pertinent property that points to a type system object associated with the exception).
The text was updated successfully, but these errors were encountered: