Community
Participate
Working Groups
I20031008 Having : int i; i= 3; Introduce param for "i= 3" ==> compile error. Introducing a param for an assignment doesn't seem to make that much sense even though it is an expression that might result in a value.
moving target milestone
It doesn't lead to compile errors in general (e.g. when assignment is to a field). We could consider raising a warning, but we should not block it if the user wants to do it. There are 2 issues: (a) raise an error when extracting an expression containing local variables or fields which are not accessible form all call sites. (b) raise a warning when extracting an assigned expression. Not for 3.0.
