False negative: DoubleCheckedLocking.ql cannot detect scenarios with ternary expressions.

**Version**
codeql 2.23.9
**Description of the issue**
When I detect the code like this using java/Likely Bugs/Concurrency/DoubleCheckedLocking.ql, the problem is reported normally:
```java

public class PosCase1 {
private Object instance; // Non-volatile field
public Object getInstance() {
if (instance == null) { // First null check
synchronized (this) { // [REPORTED LINE]
if (instance == null) { // Second null check inside synchronized block
instance = new Object(); // Initialization
}
}
}
return instance; // Return after double-checked locking
}
}
```

However, when ternary expressions are introduced into the code, DoubleCheckedLocking.ql fails to detect the problem:
```java
public class PosCase1_Var1 {
private Object instance; // Non-volatile field
public Object getInstance() {
// Use ternary for outer check, but preserve unsafe pattern
return (instance != null) ? instance : createInstance();
}
private Object createInstance() {
synchronized (this) {
if (instance == null) {
instance = new Object();
}
return instance;
}
}
}
```
These two code snippets are semantically identical, only using a ternary expression with some transformations, which is why DoubleCheckedLocking.ql cannot detect the problem.

Commencez par java/Likely Bugs/Concurrency/DoubleCheckedLocking.ql et reproduisez les deux extraits Java de l’issue afin de comparer les résultats de la requête. C’est terminé lorsque la requête signale le scénario non sûr de double-checked locking basé sur un opérateur ternaire tout en continuant à signaler le motif direct existant.

Rédigé par le modèle d'indexation à partir du texte de l'issue.