Variable Access Inside Lambdas

Direct Answer

Yes. A lambda can read and write accessible instance and static fields; the effectively-final capture rule applies to local variables and parameters, not fields. Inside an instance context, this has the same meaning as in the enclosing code. Field access is still subject to normal access-control and thread-safety rules.

Code Example

public class LambdaAccessDemo {
    private String name = "Alice";
    private static int callCount = 0;

    void showAccess() {
        String local = "local"; // captured and effectively final

        Runnable task = () -> {
            System.out.println(local);
            // local = "changed"; // does not compile

            name = "Bob";       // normal instance-field access
            callCount++;          // normal static-field access
        };
        task.run();
    }

    void showThis() {
        Runnable task = () -> System.out.println(this.name);
    }
}

The restriction applies to captured local variables and parameters. Field access follows normal Java rules. Legal field mutation can still race if tasks run concurrently.

Common Mistakes & Pitfalls

• Applying the local-capture rule to fields: fields are accessed through an object or class, so they do not have to be effectively final.
• Misreading this: in an instance context, this inside a lambda is the enclosing instance; an anonymous class body has its own this. A static context has no this to capture.
• Confusing legal access with safe access: writing a shared field is allowed by the compiler but can still create a data race.