Book Image

Java Coding Problems - Second Edition

By : Anghel Leonard
Book Image

Java Coding Problems - Second Edition

By: Anghel Leonard

Overview of this book

The super-fast evolution of the JDK between versions 12 and 21 has made the learning curve of modern Java steeper, and increased the time needed to learn it. This book will make your learning journey quicker and increase your willingness to try Java’s new features by explaining the correct practices and decisions related to complexity, performance, readability, and more. Java Coding Problems takes you through Java’s latest features but doesn’t always advocate the use of new solutions — instead, it focuses on revealing the trade-offs involved in deciding what the best solution is for a certain problem. There are more than two hundred brand new and carefully selected problems in this second edition, chosen to highlight and cover the core everyday challenges of a Java programmer. Apart from providing a comprehensive compendium of problem solutions based on real-world examples, this book will also give you the confidence to answer questions relating to matching particular streams and methods to various problems. By the end of this book you will have gained a strong understanding of Java’s new features and have the confidence to develop and choose the right solutions to your problems.
Table of Contents (16 chapters)
1
Text Blocks, Locales, Numbers, and Math
Free Chapter
2
Objects, Immutability, Switch Expressions, and Pattern Matching
14
Other Books You May Enjoy
15
Index

178. Hooking sealed classes and instanceof

Sealed classes influence how the compiler understands the instanceof operator and, implicitly, how it performs internal cast and conversion operations.

Let’s consider the following snippet of code:

public interface Quadrilateral {}
public class Triangle {}

So, we have here an interface (Quadrilateral) and a class that doesn’t implement this interface. In this context, does the following code compile?

public static void drawTriangle(Triangle t) {
  if (t instanceof Quadrilateral) {
    System.out.println("This is not a triangle");
  } else {
    System.out.println("Drawing a triangle");
  }
}

We wrote if (t instanceof Quadrilateral) {…} but we know that Triangle doesn’t implement Quadrilateral, so at first sight, we may think that the compiler will complain about this. But, actually, the code compiles because, at runtime, we may have a class Rectangle that extends Triangle...