You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to use TupleSyntax as both argument to a Select Case and as arguments to a Case clause.
Those tuple clauses each action as sub-clause, where all of the sub-clauses have to match, for the case to be consider a valid option. These sub-clause would be the current permitted clauses, with a few additional ones.
Is Nothing ' Is this sub-clause nothing?
IsNot Nothing ' Is this sub-clause not nothing?
' An empty sub-clause standing for "Not Applicable" or "I Don't Care"
Consequences
SelectCase(arg0,arg1,arg2)Case(,,)' Always TrueCaseElse' Never ExecutedEndSelect
If the compiler had some smarts, rather than lowering this to the naive implementation of a list of If Then and ElseIf ElseEnd If statements. That it could be lowered to a set of nested if statements, reducing the number of comparison checks.
The text was updated successfully, but these errors were encountered:
Tuple Sub-Clauses
I would like to use
TupleSyntax
as both argument to aSelect Case
and as arguments to aCase
clause.Those tuple clauses each action as sub-clause, where all of the sub-clauses have to match, for the case to be consider a valid option. These sub-clause would be the current permitted clauses, with a few additional ones.
Consequences
Example
Suppose we have the following class.
And then overrides a function that returns then kind of this node.
If the compiler had some smarts, rather than lowering this to the naive implementation of a list of
If Then
andElseIf
Else
End If
statements. That it could be lowered to a set of nested if statements, reducing the number of comparison checks.The text was updated successfully, but these errors were encountered: