[Reactor] Variables not updating correctly in latest-25201-2aa18550

[tunnus]

Noticed that if I try to use a case statement, I'll have to have multiple when clauses, otherwise I'll get syntax error.

(I tried to include a screenshot, but got parse error from the forum...)

The following works:

case
  when condition == true: "This is true" 
  when condition == false: "Now it is false"
  else "Something else"
end

---

But this will end up with syntax error:

case
  when condition == true: "This is true" 
  else "Something else"
end

Using build 23242 on Docker

[mgvra]

Well I stumbled across exactly the same bug and was able to resolve the problem only because @tunnus knew what was the issue.

[toggledbits]

I'll look into the issue, but two things:

1. A case with only a single when (and possibly an else) is an if statement, so why not use that? This is the workaround/recommendation. Using case in this way just seems unnecessarily complex
   .
2. Saying x == true is redundant. I see this a lot, and my old-school software guy brain just chirps a little every time. If you know x is boolean, you can just write if x then or when x then:. What you're doing is comparing true for equality to true and getting true as a result, or comparing false to true and getting back false -- you're getting out of the expression the value that you already have. I come from an era where CPU cycles and RAM were very precious commodities even in the largest systems, and my brain is still wired to remove wasted cycles like this.

[mgvra]

A case with only a single when (and possibly an else) is an if statement, so why not use that? This is the workaround/recommendation. Using case in this way just seems unnecessarily complex

Well that's true and I don't think anyone uses the case-when structure with a single when. But for example in my case, I was testing the expressions, had written only one section and was getting this mysterious syntax error. As a software engineer myself, coming from C / Java / JS background, I naturally associated the case-when structure to switch-case where it's perfectly fine to have a single case, although as you mentioned, does not make much sense.

This is not a bug that needs to be necessarily fixed ASAP, but it would be nice if you could add a clarification to the manual, stating that the case-when structure must have at least two when sections.

[toggledbits]

It'll be fixed in the next release. You are right; it should work. The bug actually arises from the else, not the single when. Oopsie!