Charlie Marsh 55d6fd53cd Treat comments on open parentheses in return annotations as dangling (#6413) ... ## Summary Given: ```python def double(a: int) -> ( # Hello int ): return 2*a ``` We currently treat `# Hello` as a trailing comment on the parameters (`(a: int)`). This PR adds a placement method to instead treat it as a dangling comment on the function definition itself, so that it gets formatted at the end of the definition, like: ```python def double(a: int) -> int: # Hello return 2*a ``` The formatting in this case is unchanged, but it's incorrect IMO for that to be a trailing comment on the parameters, and that placement leads to an instability after changing the grouping in #6410. Fixing this led to a _different_ instability related to tuple return type annotations, like: ```python def zrevrangebylex(self, name: _Key, max: _Value, min: _Value, start: int | None = None, num: int | None = None) -> ( # type: ignore[override] ): ... ``` (This is a real example.) To fix, I had to special-case tuples in that spot, though I'm not certain that's correct.		2023-08-08 16:48:38 -04:00
..
snapshots	Treat comments on open parentheses in return annotations as dangling (#6413)	2023-08-08 16:48:38 -04:00
fixtures.rs	Formatter: Add SourceType to context to enable special formatting for stub files (#6331)	2023-08-04 11:52:26 +00:00