stratozero opened a new pull request, #1455:
URL: https://github.com/apache/commons-lang/pull/1455

   <!--
     Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
     distributed with this work for additional information
     regarding copyright ownership.  The ASF licenses this file
     to you under the Apache License, Version 2.0 (the
     "License"); you may not use this file except in compliance
     with the License.  You may obtain a copy of the License at
   
       https://www.apache.org/licenses/LICENSE-2.0
   
     Unless required by applicable law or agreed to in writing,
     software distributed under the License is distributed on an
     "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
     KIND, either express or implied.  See the License for the
     specific language governing permissions and limitations
     under the License.
   -->
   
   Thanks for your contribution to [Apache 
Commons](https://commons.apache.org/)! Your help is appreciated!
   
   This PR introduces two new utility methods in `ObjectUtils` to reduce 
boilerplate 
   when executing an action only if an object is not null.
   
   ### Rationale
   - Currently, developers either write explicit null checks or use 
     `Optional.ofNullable(obj).ifPresent(...)`.
   - `Optional` adds readability but creates an extra object which is 
unnecessary 
     for simple null-guarded operations.
   - Usual null check is prone to the error of calling a getter method twice, 
(like `if (obj.getX() != null) consume(obj.getX())`), a pattern seen many times 
in a lot of projects, which is an error in many ways:
      - causes twice the access to the property
      - potentially doubles the side effects
      - can be a partial guard as it actually does not prevent the getter to 
return null in the second call
   - A static utility method in `ObjectUtils` makes the intent clearer and 
avoids 
     extra allocations.
   
   ### Proposed API
   ```java
   public static <T> void ifNotNull(T obj, Consumer<? super T> action) {
       if (obj != null) {
           action.accept(obj);
       }
   }
   ```
   
   The proposed API could then be used like `ifNotNull(obj.getX(), x -> 
consume(x))` preventing the creation of an unnecessary Optional and avoiding 
the possibility of accessing a property twice.
   
   Also, to accomplish the task of not allocating extra objects, we need to 
take care of injecting some context as a parameter (to avoid capturing lambdas):
   
   ``` java
   public static <T, C> void ifNotNull(T obj, C ctx, BiConsumer<? super T, ? 
super C> action) {
       if (obj != null) {
           action.accept(obj, ctx);
       }
   }
   ```
   
   So that it becomes possible to write `ifNotNull(obj.getX(), this, (x, ctx) 
-> XType::setContext)`
   
   -----------------------------------------
   Before you push a pull request, review this list:
   
   - [x] Read the [contribution guidelines](CONTRIBUTING.md) for this project.
   - [x] Read the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) if you use 
Artificial Intelligence (AI).
   - [ ] I used AI to create any part of, or all of, this pull request.
   - [x] Run a successful build using the default 
[Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command 
line by itself.
   - [x] Write unit tests that match behavioral changes, where the tests fail 
if the changes to the runtime are not applied. This may not always be possible, 
but it is a best-practice.
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [x] Each commit in the pull request should have a meaningful subject line 
and body. Note that a maintainer may squash commits during the merge process.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to