2023.0.102-rc released

[gfraiteur]

We have just released Metalama 2023.0.102-rc with the following improvements:

CHANGES

• BREAKING! Redesign and simplification of the invoker API.

  • Instead of method.Invokers.Final.Invoke( meta.This, a, b ) use method.Invoke( a, b ) (this is now the default target),
  • Instead of method.Invokers.Final.Invoke( a, b, c ) use method.With( a ).Invoke( b, c ) (replaces this by a as the target).
  • Instead of fieldOrProperty.Invokers.Final.GetValue( meta.This ) use fieldOrProperty.Value.
  • Instead of fieldOrProperty.Invokers.Final.SetValue( meta.This, value ) use fieldOrProperty.Value = value.

• IFieldOrProperty.ToExpression() and IParameter.ToExpression() is now redundant.

• Expression.Capture has been simplified.

For an overview of the impact of these changes, look at this commit that updates Metalama.Samples to the new API.

IMPROVEMENTS

• Contracts

  • Added eligibility condition to contract on return parameters for iterators & async
  • Assembly locator: produce uniquely-named msbuild.log

• Aspects

  • Casts introduced by a template are now marked for simplification
  • Methods like ExpressionBuilder.AddExpression now accept serializable compile-time objects

• Error reporting

  • Emit meaningful error message with partial template members
  • Diagnostic improvement: Error message for runtime/compile-time mismatch should report concrete type instead of var
  • Aspects as nested types of run-time type should report an error

• Testing and Documentation

  • Test framework: build property to force using our custom framework
  • Option to write syntax-highlighted HTML files during build

FIXES

• Capturing crash caused deadlocks, and the dump files did not generate enough information.

• Contracts

  • Contracts on parameters produce invalid code on Task async method
  • Error when using contracts on async iterator parameter
  • Async method with no return value contract does not generate await

• Aspects

  • nameof doesn't work correctly for template parameters
  • Private template fields are lost during compilation to a reference assembly
  • Can't access meta.ThisType from field initializer template
  • Reference to introduced static field qualified with aspect type instead of target type
  • Several issues with default parameter values
  • Compilation failure when attempting to introduce a get-only automatic property when the aspect is in a different assembly

• Design Time

  • Inconsistency in treating System.Index and System.Range at design time, causing duplicate generation of compile-time assemblies and invalid casts
  • Reduced memory consumption