Skip to content
← Customer Feedback for LINQPad

Settings and activity

2 results found

  1. Add ability to undo accidental language switch.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  LINQPad Feature Suggestions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Kurt Bachtold shared this idea  · 

  2. Support named tuple elements

    36 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  LINQPad Feature Suggestions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Kurt Bachtold commented  · 

    Additionally there are other issues with tuples that could be improved in LINQPad 7.

    1. when typing out a tuple deconstruct, like var (x, y) = (0, 0), the intellisense keeps trying to replace x & y with other scoped names.
    2. same with trying to create a tuple with named parameters, like var coord = (x:0, y:0).

    If LINQPad could be contextually aware in these scenarios it would be a little less disruptive to the flow of typing code. Thanks!

    Kurt Bachtold supported this idea  ·