ILSpy

9596 Commits

54 Branches

94 Tags

91 MiB

Tree: 67e22d7057

Commit Graph

Author	SHA1	Message	Date
Siegfried Pammer	67e22d7057	Flush pending side effects before materializing an operator receiver The receiver slot is appended to the current block, but the expression stack was only flushed inside the per-parameter loop - which the increment operators, taking no parameters, never enter. A side effect still pending on the stack was then emitted after the receiver read it should precede, so the increment applied to a stale value of the field it targets. Assisted-by: Claude:claude-opus-5:Claude Code	3 weeks ago
Siegfried Pammer	e4fa167afc	Render user-defined compound assignment operator declarations TypeSystemAstBuilder writes the C# 14 "operator +=" declaration form, behind a support flag like the other version-gated operator syntax; a non-public operator has no legal operator declaration (CS9308) and falls back to a plain method, except an explicit interface implementation, which is private in metadata but still written in operator form. An instance operator hides by signature like an ordinary method, so it can carry "new"; the [CompilerFeatureRequired] marker the compiler emits is removed like the other feature markers. Tooltips get the same rendering via a ConversionFlags bit; widening ConversionFlags.All also turns on the existing checked-operator and unsigned-right-shift flags, which the tooltip ambience now sets explicitly. The test fixtures land here, where the pipeline is complete end to end: pretty and IL round-trips, correctness runs against Roslyn's C# 14 binding (including the operator-inheritance matrix and a ref-local target), and the ugly configuration pins the output with the setting off. Assisted-by: Claude:claude-opus-5:Claude Code	3 weeks ago

Author

SHA1

Message

Date

Siegfried Pammer

67e22d7057

Flush pending side effects before materializing an operator receiver

The receiver slot is appended to the current block, but the expression stack
was only flushed inside the per-parameter loop - which the increment operators,
taking no parameters, never enter. A side effect still pending on the stack was
then emitted after the receiver read it should precede, so the increment
applied to a stale value of the field it targets.

Assisted-by: Claude:claude-opus-5:Claude Code

3 weeks ago

Siegfried Pammer

e4fa167afc

Render user-defined compound assignment operator declarations

TypeSystemAstBuilder writes the C# 14 "operator +=" declaration form, behind a
support flag like the other version-gated operator syntax; a non-public
operator has no legal operator declaration (CS9308) and falls back to a plain
method, except an explicit interface implementation, which is private in
metadata but still written in operator form. An instance operator hides by
signature like an ordinary method, so it can carry "new"; the
[CompilerFeatureRequired] marker the compiler emits is removed like the other
feature markers. Tooltips get the same rendering via a ConversionFlags bit;
widening ConversionFlags.All also turns on the existing checked-operator and
unsigned-right-shift flags, which the tooltip ambience now sets explicitly.

The test fixtures land here, where the pipeline is complete end to end: pretty
and IL round-trips, correctness runs against Roslyn's C# 14 binding (including
the operator-inheritance matrix and a ref-local target), and the ugly
configuration pins the output with the setting off.

Assisted-by: Claude:claude-opus-5:Claude Code

3 weeks ago

2 Commits (67e22d7057a4e62ae5236fd7cfff42e255b4a95e)