Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

Java Introduction to Functional Programming Java's Functional Toolset Function Shapes

hamsternation
hamsternation
26,615 Points

Why did the code still raise an exception if requireNonNull was supposed to "catch" the null case?

Maybe I'm not understanding this but why did the code still raise an exception? I thought the requireNonNull catches the NullPointerException and calls the CreateIssue function instead of the code actually executing and raising an exception?

1 Answer

hamsternation
hamsternation
26,615 Points

Ah nevermind, answered my own question. basically requireNonNull is still programmed to raise an exception. It's one of the functional programming methods that does the checking if something returns Null for you instead of coding it yourself.

Basically it replaces this:

If (input == null) {
do.something();
throw new IllegalArgumentException("Null input!");
} else {
code.Execute();
}
Mark Sebeck
Mark Sebeck
Treehouse Moderator 33,977 Points

I changed your comment to an answer and made it the Best Answer.