suggestion breaks when selecting lines outside of changes

[Sporarum]

🏷️ Discussion Type

Bug

Body

vyperlang/vyper#5134 (comment)
Here is what I see:

-    else:
-        # `a ** b` where neither `a` or `b` are known
-        # TODO this is currently unreachable, once we implement a way to do it safely
-        # remove the check in `vyper/context/types/value/numeric.py`
-        return
-        # `a ** b` where neither `a` or `b` are known.
-        # this is already caught by the type checker, so this branch is
-        # unreachable; panic instead of silently returning None so we fail
-        # loudly if it is ever hit.
-        raise CodegenPanic("pow requires at least one literal operand")  # pragma: nocover
+    else: #pragma: nocover
+        # type checker guarantees pow has at least one literal operand
+        raise CodegenPanic("unreachable")

But the suggestion is between the current code and the desired code, so it should be:

-    else:
-        # `a ** b` where neither `a` or `b` are known.
-        # this is already caught by the type checker, so this branch is
-        # unreachable; panic instead of silently returning None so we fail
-        # loudly if it is ever hit.
-        raise CodegenPanic("pow requires at least one literal operand")  # pragma: nocover
+    else: #pragma: nocover
+        # type checker guarantees pow has at least one literal operand
+        raise CodegenPanic("unreachable")

I had to create the sugestion manually (tripple backtick + suggestion), because the button did not show up
This appears to be because I selected one line which is outside of the current changes (else:), and is reinforced by the following:

(please ignore the indentation mismatch, that is my own mistake, I have since fixed, including in the examples above)

section 1 matches the code which is unchanged by the PR, but still part of the suggested changes
section 2 matches the code from before the PR
section 3 matches the code from the PR

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐