Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't split return type if there is a comment after function metadata. #1579

Merged
merged 2 commits into from
Oct 15, 2024
Merged

Don't split return type if there is a comment after function metadata. #1579

merged 2 commits into from
Oct 15, 2024

Commits on Oct 14, 2024

  1. Don't split return type if there is a comment after function metadata. 

    This situation rarely occurs in practice, since users typically put the
comment before the metadata too (which is why we never noticed this bug
until now).

But if it does occur, it's definitely wrong to force the return type to
split unnecessarily.
    @munificent
    munificent committed Oct 14, 2024
    Configuration menu
    Copy the full SHA
    bee1256 View commit details
    Browse the repository at this point in the history

  2. Merge branch 'main' into comment-after-metadata

    @munificent
    munificent committed Oct 14, 2024
    Configuration menu
    Copy the full SHA
    38eedb3 View commit details
    Browse the repository at this point in the history