Skip to content

error-fn-test: make processing order clearer - #236

Merged
borkdude merged 1 commit into
mainfrom
lread/error-order
Sep 25, 2026
Merged

borkdude merged 1 commit into
mainfrom
lread/error-order

Conversation

@lread

@lread lread commented Sep 25, 2026

Copy link
Copy Markdown
Contributor

Docs refer to error-fn-test as an example of collecting all errors.

This test happened to pass because :spec map size is small. For larger maps processing order, and therefore errors order, would be indeterminate.

Add comment and explicitly sort collected errors to make it clear that order is indeterminate.

Reformat expected map to make it easier to eyeball :msg values.

Closes #235

Docs refer to `error-fn-test` as an example of collecting all errors.

This test happened to pass because `:spec` map size is small.
For larger maps processing order, and therefore errors order, would be indeterminate.

Add comment and explicitly sort collected errors to make it clear that order is indeterminate.

Reformat expected map to make it easier to eyeball :msg values.

Closes #235
@borkdude
borkdude merged commit dc484b7 into main Sep 25, 2026
34 of 39 checks passed
@borkdude
borkdude deleted the lread/error-order branch September 25, 2026 17:32
@borkdude

Copy link
Copy Markdown
Contributor

Thank you, sir!

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.

Make it clearer in what order errors are generated

2 participants