#2834 closed enhancement (fixed)
Don't print attributes in type mismatch errors
| Reported by: | Per Östlund | Owned by: | Per Östlund |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.9.4 |
| Component: | Frontend | Version: | trunk |
| Keywords: | Cc: |
Description
We currently print out builtin attributes in type mismatch errors. The attributes have no influence on the type matching though, so it would be better to not print those since they clutter up the error messages.
Change History (4)
comment:1 by , 11 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → accepted |
comment:2 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
comment:3 by , 10 years ago
| Milestone: | Future → pre1.9.4 |
|---|
It doesn't make sense to keep closed ticket in the "Future" milestone that were simply forgotten to assign to the correct milestone in the past.
comment:4 by , 8 years ago
| Milestone: | pre1.9.4 → 1.9.4 |
|---|
Removing the pre1.9.4 milestone in favor of 1.9.4.
Note:
See TracTickets
for help on using tickets.
Fixed in r22431.