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
Assuming loopTo is correctly being declared a short, we can/should drop the Conversions.ToShort in the check clause and move it to the assignment clause AFAICT? Removing it from the check clause is optional, the compiler error is due to trying to implicitly assign the 32-bit integer of someArray.Length - 1 to the 16-bit short loopTo
This was fixed to match your expected output for #602, sorry it didn't get released in time for your conversion. I'll try to get it released this weekend.
I hadn't carefully checked this case, but I've now checked the decompilation eagerly coerces the loopTo variable to the control variable type (I was worried about cases where someArray.Length - 1 > short.MaxValue.
There's one remaining subtle difference from the decompilation, which is that it appears VB uses unchecked addition. I'm going to add this as a note in known limitations #16
Input code
Erroneous output
Expected output
Assuming loopTo is correctly being declared a short, we can/should drop the Conversions.ToShort in the check clause and move it to the assignment clause AFAICT? Removing it from the check clause is optional, the compiler error is due to trying to implicitly assign the 32-bit integer of someArray.Length - 1 to the 16-bit short loopTo
Details
The text was updated successfully, but these errors were encountered: