EnC Razor scenario: allow adding new lambda closures

[tmat]

MudBlazor uses the following pattern:

__builder.AddAttribute(
    8,
    "RowTemplate",
    new Microsoft.AspNetCore.Components.RenderFragment<string>(
         (context) => (__builder2) => { __builder2.AddContent(9, context); }));

Repro:

Create MAUI Blazor app.

Add to Index.razor:

@code{
    private List<string> _certificates = new List<string>() { "a", "b", "c" };
}

Ctrl+F5, add following and Hot Reload:

<MudTable T="string" Items="_certificates" Class="rounded-0" Hover="true">
    <RowTemplate>@context</RowTemplate>
</MudTable>

[danroth27]

Render fragments in Blazor are used for a couple of common use cases where a component needs to capture some Razor content that is passed as a parameter to the component and then rendered by the component:

• Child content
• Templated components

Render fragments can also be used to define reusable chunks of Razor logic, but this is less common.

@SteveSandersonMS @javiercn @MackinnonBuck We should work with @tmat to understand if there's anything we can do to evolve our API to make this scenario more hot reload friendly.