Shubham Ugare

I looked at the WALA `ShrikeCFG` implementation that we are using. `ShrikeCFG::computeEdges` for blocks which have the last instruction as a `potentially excepting instruction` adds exceptional edges to every corresponding...

If we are not gaining much information from the try block which can potentially throw a caught NPE. We can remove that block from the bytecode in the pre-processing step?

That will make it weaker. But safer than current implementation? Unless we can do something better which handles all the possible cases.

It is because the annotation for `Optional::get` call is `Non-null` we assume that the overriding is okay. ``` if (overriddenMethodReturnsNonNull && Nullness.hasNullableAnnotation(overridingMethod) && getComputedNullness(memberReferenceTree).equals(Nullness.NULLABLE)) { //throw error } ``` In...

> So is the issue here that `Nullness.hasNullableAnnotation(overridingMethod)` returns `false`? Yes. > Maybe we need to modify that conjunct to invoke the handler somehow? Yeah, that will be a little...

> Random idea. What if when Optional checking is enabled, we add a library model making `Optional.get()` return `@Nullable`, rather than trying to override the nullability in the Optional handler....

Yeah, when I turned on the flag on Uber's code, there were few some occurrences. The methods are not annotated. Though it will be much better if we could support...

Hi @victbr, Yes, you are right, I think using other languages like Rust without GIL is probably the best solution for this.

Hi @AzizCode92, SynCode doesn't support FIM models at this point. Do you have any specific application in your mind?

Yeah, it is definitely not straightforward extension of what currently exists within SynCode. In theory, one can use the constraints-based on suffix (in addition to the constraint from the prefix...