pimhwang/ILSpy - ILSpy - git.quantfans.net

Author	SHA1	Message	Date
Christoph Wille	fe9f6db3ee	Emit C# 7.1 default literals where the context supplies the type Shortening default(T) is the same problem as removing the redundant cast around a lambda whose delegate type the context already fixes, so it uses the same mechanism: ConvertTo makes the explicit type implicit when the conversion is an identity conversion and the caller allows an implicit one. The literal keeps the type it was shortened from, so any later conversion to a different type - or any context that requires an explicit type, such as an overload resolution recheck falling back to CastArguments - can spell default(T) out again. That keeps the value intact where the bare literal would change it, e.g. "object o = default(SomeStruct)", which boxes a non-null struct while "default" would be null. Because the shortened literal resolves to DefaultLiteralResolveResult, CallBuilder's existing overload resolution recheck sees a real default literal and rejects ambiguous calls on its own; no separate bookkeeping about which arguments may stay untyped is needed. Only the contexts that supply no target type at all restore the explicit form: an awaited expression, and arguments of operator methods, which later become operator or cast syntax rather than calls. Assisted-by: Claude:claude-opus-5[1m]:Claude Code	4 weeks ago
Daniel Grunwald	59d8ae904b	Fix tests on Windows with legacy csc. There's an additional local variable when decompiling the non-optimized code; and explicitly putting that variable into the test case just makes it fail due to yet another additional variable.	4 weeks ago
Christoph Wille	471d58550c	Merge the load-bearing-cast await shapes into the main fixture They were split out only because they were failing; there is no reason to keep a second fixture now that they pass. Folding them in also widens their coverage from roslyn4OrNewer to every defaultOptions config -- legacy csc, Roslyn 1.3.2 onwards and the net40 targets -- with the 'in'-receiver extension gated on CS72 because that one needs C# 7.2. IAwaitable and ClassAwaitable were declared identically in both files and collapse into one declaration. Assisted-by: Claude:claude-opus-5[1m]:Claude Code	4 weeks ago
Siegfried Pammer	d8aca3f113	Add an async/await pattern test suite for ExpressionBuilder.VisitAwait The await surface had almost no fixture coverage beyond Task/ValueTask: every GetAwaiter in the corpus was an instance method on the awaited type itself, so the conversion VisitAwait applies to the operand was never exercised for an inherited, interface-typed or extension-method awaiter. Probing that surface turned up eight defects, all of which produce C# that does not compile. AsyncAwaitPatterns pins the shapes that do round-trip, along the three axes the translation actually depends on: the GetAwaiter receiver, the operand expression, and the context the await sits in. Its Correctness twin pins what Pretty cannot see - copy semantics of struct awaitables and the evaluation order around the suspension point. AsyncAwaitPatternsBugs is the spec for the defects, written as the C# that ought to come out, with the current wrong output named per member. It fails today; that is the point, and fixing a defect is meant to delete a comment rather than edit an expectation. Assisted-by: Claude:claude-opus-5[1m]:Claude Code	4 weeks ago