You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like we could teach the type visitor to walk the debug info, instead of using visit glue. I don't know if this is a worthwhile idea, but it does seem feasible... It depends on how lossy the debugging information is.
The text was updated successfully, but these errors were encountered:
fix [`manual_flatten`] help texts order
fixesrust-lang#8948
Whenever suggestion for this lint does not fit in one line,
legacy solution has some unexpected/unhandled behavior:
lint will then generate two help messages which seem to be shown in the wrong order.
The second help message in that case will contain the suggestion.
The first help message always refers to a suggestion message,
and **it should adapt** depending on the location of the suggestion:
- inline suggestion within the error/warning message
- suggestion separated into a second help text
This is my first contribution here, so I hope I didn't miss anything for creating this PR.
changelog: fix [`manual_flatten`] help texts order
It seems like we could teach the type visitor to walk the debug info, instead of using visit glue. I don't know if this is a worthwhile idea, but it does seem feasible... It depends on how lossy the debugging information is.
The text was updated successfully, but these errors were encountered: