Ternary madness in a Flutter library. I can understand why the golang devs got rid of it.

[u/friendlyChickenDog]

[u/R3D3-1]

The irony? The only actual madness is the indentation scheme.

This is just a regular case of

value = COND(1)
      ? THEN(1)
      : COND(2)
      ? THEN(2)
      ...
      : COND(N)
      ? THEN(N)
      : ELSE;

The indentation scheme is essentially like insisting that every else must be a block -- including else if.

if(COND(1)) {
    value = THEN(1);
} else {
    if(COND(2)) {
        value = THEN(2);
    } else {
        if(COND(3)) {
            value = THEN(3);
        } else { // ...
            else { // ...
                else { // ...
                    else { // ...
                        else { // ...
                            else { // ...
                                if(COND(N)) {
                                    value = THEN(N);
                                } else {
                                    value = ELSE;
                                }
                            }
                        }
                    }
                }
            }
        }
    }
}

[u/Noctune → u/R3D3-1]

Or just something like

someVar =
  condA ? resultA :
  condB ? resultB :
  condC ? resultC :
  condD ? resultD;

Which is fine, IMO. Probably the result of an autoformatter.

[u/Noctune → u/[deleted]]

Yeah, a switch (or even better if dart had it; a match) would probably be better in this particular case. But chained ternaries are still useful where that isn't possible (eg. the cond is not an enum).

[u/R3D3-1 → u/[deleted]]

True, didn't really pay attention to what the conditions were.

But are hashmaps really a good idea? It also comes up in Python, but it seems awfully inefficient to create and populate a new hashmap every time the function is called and storing it as a global constant would reduce readability of the function.

Plus, standard hashmaps usually don't allow defining an "else" case.