Lambda expressions were introduced in Java 8 to simplify the writing of functional interfaces. 1. The basic syntax is (parameters) -> { body }, and parameter types or brackets can be omitted according to the situation. For example, if there is no parameter, use () -> System.out.println("Hello"), use x -> System.out.println(x), use multiple parameters (x, y) -> xy; 2. The lambda can be assigned to functional interfaces such as Runnable, Consumer or Function, which replaces anonymous class writing and improves readability; 3. It is often used in combination with collections and Stream APIs, such as forEach, filter, map, etc., to make the code more concise and clear; 4. Use parameter types in combination with type inference to improve code simplicity; 5. Use method references (such as System.out::println) instead of lambdas that only call a single method, further reducing redundant code. Rational use of lambda can improve Java development efficiency and code quality.
Lambda expressions were introduced in Java 8, and they brought a more concise way to write instances of functional interfaces —interfaces with only one abstract method. If you're looking to simplify your code or work with streams and modern Java features, lambdas are essential.

Here's how to use them effectively.

Understanding the Basic Syntax
The basic structure of a lambda expression is:
(parameters) -> { body }
Depending on the situation, parts of this can be omitted for brevity.

- No parameters :
() -> System.out.println("Hello")
- One parameter :
x -> System.out.println(x)
- Multiple parameters :
(x, y) -> xy
You can assign these directly to functional interfaces like Runnable
, Consumer
, or Function
.
For example:
Runnable r = () -> System.out.println("Running...");
This replaces the older anonymous class style:
Runnable r = new Runnable() { public void run() { System.out.println("Running..."); } };
It's cleaner and easier to read, especially when passing behavior as arguments.
Using Lambdas with Collections and Streams
One of the most common uses of lambda expressions is with Java Streams , which were also introduced in Java 8.
If you have a list and want to process each element, instead of writing a loop, you can do something like:
List<String> names = Arrays.asList("Alice", "Bob", "Charlie"); names.forEach(name -> System.out.println(name));
Or filter elements:
names.stream() .filter(name -> name.startsWith("A")) .forEach(System.out::println);
This makes it easy to chain operations and keep your logic clear.
Some key interfaces to know when working with lambdas and streams:
-
Predicate<T>
– used for filtering (test
method) -
Function<T, R>
– used for mapping (apply
) -
Consumer<T>
– for side effects (accept
) -
Supplier<T>
– for lazy evaluation (get
)
Each of these can be implemented using a lambda, without needing custom classes.
Leveraging Type Inference and Method References
Java can often infer types from context, so you don't always need to specify them explicitly.
Instead of:
List<String> filtered = names.stream() .filter((String name) -> name.length() > 3) .toList();
You can just write:
List<String> filtered = names.stream() .filter(name -> name.length() > 3) .toList();
Also, if your lambda just calls an existing method, you can replace it with a method reference :
names.forEach(System.out::println);
Which is shorter than:
names.forEach(x -> System.out.println(x));
Method references come in a few forms:
-
ClassName::staticMethod
-
object::instanceMethod
-
ClassName::instanceMethod
(used when the first argument is the instance)
They help reduce visual noise and improve readingability.
Using lambda expressions doesn't have to feel complex. Start with simple cases like replacing anonymous classes or iterating over collections, and gradually move into more advanced stream operations. Just remember to keep your lambdas short and focused — ideally doing only one thing.
Once you get used to them, they become a natural part of your Java toolkit.
Basically that's it.
The above is the detailed content of How to use lambda expressions in Java?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Java supports asynchronous programming including the use of CompletableFuture, responsive streams (such as ProjectReactor), and virtual threads in Java19. 1.CompletableFuture improves code readability and maintenance through chain calls, and supports task orchestration and exception handling; 2. ProjectReactor provides Mono and Flux types to implement responsive programming, with backpressure mechanism and rich operators; 3. Virtual threads reduce concurrency costs, are suitable for I/O-intensive tasks, and are lighter and easier to expand than traditional platform threads. Each method has applicable scenarios, and appropriate tools should be selected according to your needs and mixed models should be avoided to maintain simplicity

In Java, enums are suitable for representing fixed constant sets. Best practices include: 1. Use enum to represent fixed state or options to improve type safety and readability; 2. Add properties and methods to enums to enhance flexibility, such as defining fields, constructors, helper methods, etc.; 3. Use EnumMap and EnumSet to improve performance and type safety because they are more efficient based on arrays; 4. Avoid abuse of enums, such as dynamic values, frequent changes or complex logic scenarios, which should be replaced by other methods. Correct use of enum can improve code quality and reduce errors, but you need to pay attention to its applicable boundaries.

JavaNIO is a new IOAPI introduced by Java 1.4. 1) is aimed at buffers and channels, 2) contains Buffer, Channel and Selector core components, 3) supports non-blocking mode, and 4) handles concurrent connections more efficiently than traditional IO. Its advantages are reflected in: 1) Non-blocking IO reduces thread overhead, 2) Buffer improves data transmission efficiency, 3) Selector realizes multiplexing, and 4) Memory mapping speeds up file reading and writing. Note when using: 1) The flip/clear operation of the Buffer is easy to be confused, 2) Incomplete data needs to be processed manually without blocking, 3) Selector registration must be canceled in time, 4) NIO is not suitable for all scenarios.

HashMap implements key-value pair storage through hash tables in Java, and its core lies in quickly positioning data locations. 1. First use the hashCode() method of the key to generate a hash value and convert it into an array index through bit operations; 2. Different objects may generate the same hash value, resulting in conflicts. At this time, the node is mounted in the form of a linked list. After JDK8, the linked list is too long (default length 8) and it will be converted to a red and black tree to improve efficiency; 3. When using a custom class as a key, the equals() and hashCode() methods must be rewritten; 4. HashMap dynamically expands capacity. When the number of elements exceeds the capacity and multiplies by the load factor (default 0.75), expand and rehash; 5. HashMap is not thread-safe, and Concu should be used in multithreaded

Java enumerations not only represent constants, but can also encapsulate behavior, carry data, and implement interfaces. 1. Enumeration is a class used to define fixed instances, such as week and state, which is safer than strings or integers; 2. It can carry data and methods, such as passing values ??through constructors and providing access methods; 3. It can use switch to handle different logics, with clear structure; 4. It can implement interfaces or abstract methods to make differentiated behaviors of different enumeration values; 5. Pay attention to avoid abuse, hard-code comparison, dependence on ordinal values, and reasonably naming and serialization.

Singleton design pattern in Java ensures that a class has only one instance and provides a global access point through private constructors and static methods, which is suitable for controlling access to shared resources. Implementation methods include: 1. Lazy loading, that is, the instance is created only when the first request is requested, which is suitable for situations where resource consumption is high and not necessarily required; 2. Thread-safe processing, ensuring that only one instance is created in a multi-threaded environment through synchronization methods or double check locking, and reducing performance impact; 3. Hungry loading, which directly initializes the instance during class loading, is suitable for lightweight objects or scenarios that can be initialized in advance; 4. Enumeration implementation, using Java enumeration to naturally support serialization, thread safety and prevent reflective attacks, is a recommended concise and reliable method. Different implementation methods can be selected according to specific needs

Optional can clearly express intentions and reduce code noise for null judgments. 1. Optional.ofNullable is a common way to deal with null objects. For example, when taking values ??from maps, orElse can be used to provide default values, so that the logic is clearer and concise; 2. Use chain calls maps to achieve nested values ??to safely avoid NPE, and automatically terminate if any link is null and return the default value; 3. Filter can be used for conditional filtering, and subsequent operations will continue to be performed only if the conditions are met, otherwise it will jump directly to orElse, which is suitable for lightweight business judgment; 4. It is not recommended to overuse Optional, such as basic types or simple logic, which will increase complexity, and some scenarios will directly return to nu.

The core workaround for encountering java.io.NotSerializableException is to ensure that all classes that need to be serialized implement the Serializable interface and check the serialization support of nested objects. 1. Add implementsSerializable to the main class; 2. Ensure that the corresponding classes of custom fields in the class also implement Serializable; 3. Use transient to mark fields that do not need to be serialized; 4. Check the non-serialized types in collections or nested objects; 5. Check which class does not implement the interface; 6. Consider replacement design for classes that cannot be modified, such as saving key data or using serializable intermediate structures; 7. Consider modifying
