{"id":21079,"date":"2022-11-12T01:19:34","date_gmt":"2022-11-11T19:49:34","guid":{"rendered":"https:\/\/jassweb.com\/solved\/solved-java-lambda-consumer-compilation-behavior\/"},"modified":"2022-11-12T01:19:34","modified_gmt":"2022-11-11T19:49:34","slug":"solved-java-lambda-consumer-compilation-behavior","status":"publish","type":"post","link":"https:\/\/jassweb.com\/solved\/solved-java-lambda-consumer-compilation-behavior\/","title":{"rendered":"[Solved] Java Lambda Consumer Compilation behavior"},"content":{"rendered":"

[ad_1]
\n<\/p>\n

\n
\n
<\/div>\n
\n
\n

The problem is that your two lambdas could be using the value of datamap<\/code> before it has been initialized. At least, that is what the JLS definite assignment rules are saying.<\/p>\n

This is what will happen when the ConsumerTest<\/code> object is created:<\/p>\n

    \n
  1. The bare object is allocated.<\/li>\n
  2. The superclass constructor is called (Object()<\/code>) which does nothing.<\/li>\n
  3. The instance field declarations are “executed”\n
      \n
    1. dataMap<\/code> … not initialized<\/li>\n
    2. allConsumers<\/code> … not initialized<\/li>\n
    3. evenConsumer<\/code> … initialized to the value of the first lambda<\/code><\/li>\n
    4. oddConsumer<\/code> … initialized to the value of the second lambda<\/code><\/li>\n<\/ol>\n<\/li>\n
    5. The body of the constructor is executed\n
        \n
      1. dataMap<\/code> is initialized<\/li>\n
      2. allConsumers<\/code> is initialized.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

        The problem is (conceptually) this. Those lambdas could in theory be passed anywhere as soon as they have been initialized. If the recipient decides to use them before<\/em> the dataMap<\/code> variable has been initialized, then what would the lambdas see?<\/p>\n