Yes, because there is no longer special-case handling for `UnitClass` below. If we have
```def freshname = { val hoho = "hoho" }```
this parses just fine, and the statement is of type `Unit`. That was the problem with my first attempt at this bug. On the other hand if we have
```def freshname = val hoho = "hoho"```
this fails to parse, which yields `NoSymbol` and falls through to `asDefn()`.

I think this is a more correct way to distinguish between expressions and statements.