The new error message "Unused, non public field" shows up even in cases like this:
src/Session.fz:176:7: error 2: Unused, non public field 'e'
e error => panic "error reading from path: {file}"
To solve this, either
- use the field
- make it 'public'
or
- explicitly ignore the result '_ := …'
where (in this example) a match is present. For cases like this, and likewise for all cases where the field is scoped, the error message should not suggest to make the field public because that will not make sense.
The new error message "Unused, non public field" shows up even in cases like this:
where (in this example) a
matchis present. For cases like this, and likewise for all cases where the field is scoped, the error message should not suggest to make the fieldpublicbecause that will not make sense.