Jon Sequeira

Are you running an older version of `dotnet-try`? Try this: ```console > dotnet tool uninstall -g dotnet-try > dotnet tool install -g Microsoft.dotnet-try ```

This is actually a bug here. .NET Interactive will handle this correctly because the default formatters will check for recursion correctly. `dotnet-repl` has different formatter implementations targeting Spectre.Console.

This is fixed in version 0.1.30.

This is actually not fixed for records. The underlying issue here is one with `ToString` when records have reference cycles. See: https://github.com/dotnet/roslyn-analyzers/issues/5068

The formatters do recursive evaluation but they also have built-in recursion controls, e.g.:  Does this repro on the latest version and does it repro in a .NET Interactive notebook?...

Here's a non-recursive example comparing the formatter to the `ToString` output:  The formatter output is definitely a little redundant. Let's look at the larger goal of using formatters instead...

`Ctrl-Up` and `Ctrl-Down` will let you navigate through your current session's submission history. I'd like to add support for `Up` and `Down` but I think it needs to happen in...

This capability is something we're looking at enabling for .NET Interactive generally (including for notebooks): https://github.com/dotnet/interactive/issues/890. If the scenarios you have in mind aren't captured there, please add your thoughts.

This happens because what appears to be a local variable in C# scripting is implemented as a field.

Here's the related issue in Roslyn: https://github.com/dotnet/roslyn/issues/40213