Vote for the default style of list/record/match branches/parameter list/type parameters

[blindFS]

We want to collect preferences from different users on this topic.

Related issues #16 #30

[blindFS]

Examples of match branch

match $foo {
  1 => 1
  true => 2
}

match $foo { 1 => 1 true => 2 }

match $foo {
  1 => 1,
  true => 2,
}

match $foo { 1 => 1, true => 2 }

Examples of parameter list

def foo [bar: bool baz: record<a: int, b: bool>] { }
{|foo bar| $foo}

def foo [
  bar: bool
  baz: record<a: int, b: bool>
] { }

def foo [bar: bool, baz: record<a: int, b: bool>] { }
{|foo, bar| $foo}

def foo [
  bar: bool,
  baz: record<a: int, b: bool>,
] { }

[Bahex]

In multi line expressions, the last item should have a trailing comma too (reduces noise in diffs, can make batch editing simpler)

[Juhan280]

My personal preferance: no comma unless its a single line record/match expression/parameter list

[Juhan280]

Yes, except that pr also adds commas in single line list. But for me personally, single line list with just space delimeter is readable. But single line records/match/etc without comma looks confussing

[blindFS]

I see, you want both option 3 and option 4. Thanks for sharing your design.

[blindFS]

Yes, except that pr also adds commas in single line list. But for me personally, single line list with just space delimeter is readable. But single line records/match/etc without comma looks confussing

I respect your choice for single-line list, just want to remind you that the list example above might be too simple, I don't know if something like [(echo foo) [bar baz]] will change your mind.

[Juhan280]

Nah, I already considered this case. Here we are using brackets and so there is no confussion

[blindFS]

Nah, I already considered this case. Here we are using brackets and so there is no confussion

Fair point.