pimhwang/ILSpy - ILSpy - git.quantfans.net

Author	SHA1	Message	Date
Siegfried Pammer	90d563b796	Walk the step tree with the helper the repo already has Three copies of the same pre-order walk across two test files become TreeTraversal.PreOrder, and the stepper fixture builds its decompiler through the file-name constructor instead of assembling the type system by hand. Assisted-by: Claude:claude-opus-5[1m]:Claude Code	3 weeks ago
Siegfried Pammer	b8d68d9143	Give the builder output a step of its own The state the ExpressionBuilder and StatementBuilder leave behind was only reachable as "state before the first AST transform" - an entry that names a transform rather than the state, and that sits below every member's group in a tree with one group per member. It is now a top-level step at the seam, where the whole type is converted and nothing has transformed it yet. Assisted-by: Claude:claude-opus-5[1m]:Claude Code	3 weeks ago
Siegfried Pammer	0b4b2a3f08	Record the whole pipeline or none of it Recording only gated the IL half, so a run with it off still numbered the C# AST transforms into the shared stepper. That gave one pipeline two numbering scales, and a step index is only meaningful against the scale it was recorded on: a tree captured under one and replayed under the other selects a different step. It also let the crashed-member attribution fire on a counter that had never moved - a limit of zero matched at every throwing transform and rendered an unrelated member's ILAst. The flag now gates both halves, so steps exist exactly when recording is on, and it lives on the pane instance rather than a static the background decompile read across threads. Assisted-by: Claude:claude-opus-5[1m]:Claude Code	3 weeks ago
Siegfried Pammer	a5bd230e14	Walk the whole decompiler pipeline in the Debug Steps pane The pane used to split the pipeline across two languages: the ILAst language stepped the IL transforms, the C# language stepped the AST transforms, and nothing showed the seam between them, so a step index meant a different thing depending on which language happened to be selected. Recording both halves into one Stepper makes an index replayable across the whole pipeline; a limit that lands in the IL phase has no C# to print, so the halted function is rendered as ILAst instead. Which function that is takes some care, because a member group's EndStep is the next member's first step: a halt standing on a member's opening step belongs to the member that just finished, a transform that throws where the limit was aimed has to hand over the ILAst it half-transformed (what the ILAst language showed as "ILAst after the crash"), and a step recorded on a helper function the pipeline has not attached yet belongs to that function's own tree. Retention stays opt-in twice over: the decompiler records IL steps only when asked to, and the pane asks only while its view is on screen. Every kept step pins the ILAst it captured, which for one type runs to tens of thousands of nodes, so a closed pane would be paying for a tree nobody displays. What is left of the ILAst language is its typed-IL dump, which runs no transforms at all. That stays, as TypedILLanguage. IDebugStepProvider was down to a single implementation and is removed. Assisted-by: Claude:claude-opus-5[1m]:Claude Code	3 weeks ago