-
Notifications
You must be signed in to change notification settings - Fork 847
[WIP] Adding extra detail to error messages #1454
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
Merged
Merged
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
87e5f46
added detail to local.fs error messages
cloudRoutine 85669c4
move detailed exceptions into FSharp.Core namespace
cloudRoutine 10ef89e
detailed error messages for array2.fs
cloudRoutine 7e577e0
Detailed error messages seq.fs
cloudRoutine 033f04d
added detail to 2 string errors in string.fs
cloudRoutine 945d529
Added more detailed error messages to list.fs
cloudRoutine c0200bf
cleaned up error messages in local.fs
cloudRoutine 9e03583
extend detailed exception signature
cloudRoutine 65907ec
Clean up Array2D error messages
cloudRoutine cdfa813
more detailed collections function error messages
cloudRoutine 3ccf2fe
adjust access modifiers
cloudRoutine b5198b0
fix grammar in error message
cloudRoutine ff890d8
use labeled properties for FsCheck tests
cloudRoutine 4ef509b
show results in fscheck labels
cloudRoutine ddc37f3
additional exn fns for arrays
cloudRoutine ab6f346
added more detailed array error messages
cloudRoutine bdc2ea6
check exns explicitly with FsCheck
cloudRoutine 6ac848a
simplify error messages in seq.fs
cloudRoutine 467fb8c
PR cleanup
cloudRoutine File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
282 changes: 160 additions & 122 deletions
282
...p.Core.Unittests/FSharp.Core/Microsoft.FSharp.Collections/CollectionModulesConsistency.fs
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I gather that error message will now report bound per dimensions when there is a mismatch, should tests be added to assert this behaviour does what is intended wrt. new error messages?