The usual handling in Rust afterwards is in most cases log one error or return to upstream “there was an error”. In some rare cases all errors returned as a single case.
Both of these first are bad for i18n and finding what’s really happened in the middle.
In that for, all error messages have been lost. If to add such output “for” is the most elegant solution.
No they’re in the resulting iterator
The usual handling in Rust afterwards is in most cases log one error or return to upstream “there was an error”. In some rare cases all errors returned as a single case.
Both of these first are bad for i18n and finding what’s really happened in the middle.