Hi Jochen,
Thanks a lot for your detailed explanation block by block!
> If you use the Closure code, then variables used in Closures are marked
> as Reference even if they are only read
According to your suggestion, I've fixed the loading variable issue[1]
:-)
Thanks for you
Just one more thing.
On Tue, Jan 16, 2018 at 10:56 AM, Paul King wrote:
> 1) for me, if you have to explain a name better, then it is already a bad
>> name. Intuitively suggesting the correct interpretation to another
>> developer, without requiring him to thoroughly read through the
>> document
Explanations below.
On Tue, Jan 16, 2018 at 12:56 AM, MG wrote:
> Hi Paul,
>
> 1) for me, if you have to explain a name better, then it is already a bad
> name. Intuitively suggesting the correct interpretation to another
> developer, without requiring him to thoroughly read through the
> docume
Am 15.01.2018 um 10:53 schrieb Daniel Sun:
Hi Jochen,
`ArrayIndexOutOfBoundsException` is fixed. I encounter another
problem(i.e. How to load arguments according to some specified order): I
want to load local variables[1] according to the order in which the local
variables appear in lamb
Hi Jochen,
I still have a quesiton: How can I load variables via Groovy
utilities? Here[1] is my current way to load varaibles, it is not correct
though it can compile and run(i.e. the related test can not pass[2]):
I tried the following way, but error occurred[3]...
```
int
Hi Paul,
1) for me, if you have to explain a name better, then it is already a
bad name. Intuitively suggesting the correct interpretation to another
developer, without requiring him to thoroughly read through the
documentation, is the art of picking good names (which imho Groovy
overall does
Am 15.01.2018 um 15:21 schrieb Daniel Sun:
Hi Jesper,
Thanks for your advice :-)
That's much easier than making the order dependent on the usage.
Actually javac makes the order dependent on the local variables usage
in the lambda body. I'll follow its way for the time being bec
Hi Jesper,
Thanks for your advice :-)
> That's much easier than making the order dependent on the usage.
Actually javac makes the order dependent on the local variables usage
in the lambda body. I'll follow its way for the time being because I can
reference how it make lambda work ;-)
Response below.
On Sun, Jan 14, 2018 at 6:11 AM, MG wrote:
> Hi Paul,
>
> now I get where you are coming from with @KnownImmutable. I agree with
> splitting the two concepts: Flexible & elegant :-)
>
> Transferring the parameter name knownImmutables (which exists inside the
> @Immutable context)
Hi Daniel
> On 15 Jan 2018, at 10.53, Daniel Sun wrote:
>
> Hi Jochen,
>
> `ArrayIndexOutOfBoundsException` is fixed. I encounter another
> problem(i.e. How to load arguments according to some specified order): I
> want to load local variables[1] according to the order in which the local
>
Hi Jochen,
`ArrayIndexOutOfBoundsException` is fixed. I encounter another
problem(i.e. How to load arguments according to some specified order): I
want to load local variables[1] according to the order in which the local
variables appear in lambda body. For example:
(1)
```
String x =
11 matches
Mail list logo
