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
If the value on which to type-switch was already set (i.e. a variable),
there was no problem. But if it had to be obtained through a complex
expression (func call, array index, etc...), then the code to retrieve
the value prior type-switch was not scheduled. This is now fixed.
The issue it fixes is nasty because the behavior was silently changed,
leading to further unrelated issues or panics.
Fixestraefik#1444.
If the value on which to type-switch was already set (i.e. a variable),
there was no problem. But if it had to be obtained through a complex
expression (func call, array index, etc...), then the code to retrieve
the value prior type-switch was not scheduled. This is now fixed.
The issue it fixes is nasty because the behavior was silently changed,
leading to further unrelated issues or panics.
Fixestraefik#1444.
If the value on which to type-switch was already set (i.e. a variable),
there was no problem. But if it had to be obtained through a complex
expression (func call, array index, etc...), then the code to retrieve
the value prior type-switch was not scheduled. This is now fixed.
This issue is nasty because the behavior is silently changed,
leading potentially to further unrelated issues or runtime panics.
Fixes#1444.
The following program
sample.go
triggers an unexpected resultExpected result
Got
Yaegi Version
v0.14.1
Additional Notes
This issue is related to #1426.
The text was updated successfully, but these errors were encountered: