Julien Couvreur

icon indicating a website link http://blog.monstuff.com icon indicating an email [email protected]

icon company Microsoft icon location Seattle, WA icon location Language Designer and Compiler Developer on the Roslyn (C# and VB.Net) team.

Results 152 comments of Julien Couvreur

Emit and roundtrip underlying instance field

@AlekseyTs @jjonescz for review. Thanks

Emit and roundtrip underlying instance field

Opened corresponding spec PR [https://github.com/dotnet/csharplang/pull/8121](https://github.com/dotnet/csharplang/pull/8121) --- In reply to: [2108098258](https://github.com/dotnet/roslyn/pull/73407#issuecomment-2108098258) [](http://example.com/codeflow?ancestors=2108098258)

Missing CS8970 when applying attribute alias with unsupported type substitution

@RikkiGibson for triage. Thanks

Add proposal for partial type inference

Sorry for the delay. We've focused on wrapping up C# 12 bugs. We'll look in a few weeks. Thanks

Open issue: relax requirement that type be enumerable to participate in collection expressions

Here's the roslyn example that prompted this issue: https://github.com/dotnet/roslyn/pull/71134 Having a dummy/unused `IEnumerable` implementation seems superfluous.

Collection expression loophole: ability to invoke .Add() method with the parameter type not matching the collection expression element type

I believe this is by-design from current spec. There exists a conversion from `default` to the iteration type `int` and `default` can also be used to invoke `.Add`. Those two...

Champion "Async Main" (C# 7.1)

Some LDM notes: * https://github.com/dotnet/csharplang/blob/master/meetings/2017/LDM-2017-04-18.md#asynchronous-main

Champion "Async Main" (C# 7.1)

FYI @TyOverby For question above

Inherit documentation for positional C# record parameters from an interface

Added labels per https://github.com/dotnet/roslyn/blob/main/docs/contributing/API%20Review%20Process.md

[dotnet-sdk-8.0.100-preview.1.23107.4] Custom class "Windows" result to its elements cannot be recognized in .NET 8.0

> So the order of namespace resolution had changed in the latest c# version I don't think that's the case. We've not made such changes. > the language seems to...