ILSpy

Commit Graph

Author	SHA1	Message	Date
Siegfried Pammer	5d49a2f751	Simplify hoisted null-guard fold to reference-type constructor chains A value-type constructor chains via 'this = new TSelf(...)', an ordinary body statement, so a hoisted argument null-guard in front of it is legal C# output as-is; folding it back only bought lifting the chain into a this(...) initializer. That cosmetic gain does not justify the extra stobj shape matching, so the guard now stays in the body for structs and the gate reduces to the ChainedConstructorCallILOffset check. Assisted-by: Claude:claude-fable-5:Claude Code	2 days ago
Siegfried Pammer	a1f9a6b6f5	Fix #3824 : fold a hoisted argument null-guard at the ILAst level When a chained constructor-call argument contains a throwing null-check (e.g. `value?.Length ?? throw ...`) and the argument is evaluated more than once, the compiler hoists the null-check in front of the chained call. The hoisted `if (value == null) throw ...;` then became the first body statement, so MoveConstructorInitializer could not recognize the chained call and left it as an illegal in-body `base..ctor(...)` / `this..ctor(...)` (a parse error). Fix it in the ILAst, where the `?? throw` shape already lives, rather than re-deriving it on the C# AST: NullCoalescingTransform folds a guard that directly precedes the chained call back into the first use of the parameter as `if.notnull(ldloc param, throw)`. Nothing in a constructor body can legally run before the chained call, so a statement preceding it is necessarily compiler-hoisted; matching is by ILVariable identity, not parameter name. The guard disappears before the AST transforms run, so they need no change. Reference types chain via a base/this..ctor CallInstruction; value types chain via `this = new TSelf(...)`, i.e. stobj(ldthis, newobj TSelf(...)), which ChainedConstructorCallILOffset does not report -- so the value-type chain (including the case where this is spilled to a stack slot because the guard sits between its load and the call) is matched directly. Assisted-by: Claude:claude-opus-4-8:Claude Code	3 days ago
Peter Crabtree	e1e16b64f5	dev: Strip BOM mark from text files	10 months ago
dotnet format	0d9f871a4f	#2128 : Reformat the whole code base.	6 years ago
Daniel Grunwald	2acc4339df	#2058 : Mark most transforms as public to help users that use the ILAst directly without decompiling to C#.	6 years ago
Siegfried Pammer	65f9fe1076	Remove unused code.	7 years ago
Siegfried Pammer	fd24b5ea26	Simplify check for addresses	7 years ago
Siegfried Pammer	c0f954aaa6	Simplify nullable value types throw expression pattern.	7 years ago
Siegfried Pammer	50c4fa1c13	Add two more patterns with throw expressions.	7 years ago
Siegfried Pammer	7d4b4c6433	Implement NullCoalescingTransform with value types.	7 years ago
Siegfried Pammer	c6f4f77b57	Reorder code in NullCoalescingTransform.cs	7 years ago
Siegfried Pammer	875af13934	Fix #750 : Missing recognizer for ?? when rhs is an assignment expression	8 years ago
Daniel Grunwald	58b0ddda9e	Add ThrowExpressionConversion.	8 years ago
Daniel Grunwald	21d3881e37	Introduce named arguments only in the statement transform. Don't use extension method syntax when 'this' parameter of extension method is named.	8 years ago
Andreas Weizel	a254913624	Work for throw expressions.	8 years ago
Daniel Grunwald	ca0fa55af8	Implement null propagation transform.	9 years ago
Daniel Grunwald	7017c6f6e6	Replace LoopingBlockTransform with StatementTransform. This transform interleaves statement-combining transforms so that nested structures can be detected better.	9 years ago
Daniel Grunwald	4830b37ab9	[nullables] Add support for '??' operator on nullables.	9 years ago
Daniel Grunwald	33099c5d65	[nullables] Extend nullable lifting to arbitrary combinations of 'conv' and 'binary.numeric'.	9 years ago
Siegfried Pammer	bcaf6db313	Fix use of Clone in NullCoalescingTransform	9 years ago
Siegfried Pammer	5007c660ca	Add NullCoalescingInstruction	9 years ago

22 Commits (07d5a01d2bb30c50a6daaf80fce059bfaf4ffbf8)