dyno: Begin resolving method calls and initializer calls

[dlongnecke-cray]

dyno: Begin resolving method calls and new calls (#19359)

Begin resolving method calls and new calls in the dyno resolver.
The goal is to handle simple cases such a record with a zero argument
primary or secondary method, or a 'new r' for a record 'r'.

When resolving a 'new' expression also resolve an initializer call
as a side effect.

FUTURE WORK

• Resolve class types and class management
• Use the resulting initializer to compute the final 'new' type
• If the initializer is not compiler-generated, resolve the body
  in order to determine the final type
• Tests for generic/param types
• Verify that POI stuff is working as expected in tests

Reviewed by @mppf. Thanks!

Signed-off-by: David Longnecker dlongnecke-cray@users.noreply.github.com

[mppf]

I'd like to see slightly more effort for draft code computing the POI details before merging. I'm not expecting that is too hard (just do a similar thing to the normal call resolution process).

[mppf]

I think you mean, TODO: also adjust poiInfo.

Seems to me you could make something based on this existing code:

  if (anyInstantiated) {
    instantiationPoiScope =
      pointOfInstantiationScope(context, inScope, inPoiScope);
    poiInfo.setPoiScope(instantiationPoiScope);
  }

  for (const TypedFnSignature* candidate : mostSpecific) {
    if (candidate != nullptr) {
      if (candidate->untyped()->idIsFunction()) {
        accumulatePoisUsedByResolvingBody(context, candidate,
                                          instantiationPoiScope, poiInfo);
      }
    }
  }