ILSpy

9333 Commits

54 Branches

94 Tags

91 MiB

Tree: fe147ce211

Commit Graph

Author	SHA1	Message	Date
Siegfried Pammer	fe147ce211	Port IdStringProvider.GetIdString to SRM Generate ID strings directly from metadata instead of the type system, so callers holding only a MetadataFile and an EntityHandle do not need to materialize a compilation first, and raw metadata names survive verbatim. GetIdString(IEntity) stays as a thin wrapper over the new implementation, keeping the published entity-based entry point intact. The implementation is validated by a differential suite comparing every symbol of a test corpus against Roslyn's GetDocumentationCommentId. Corners pinned by those tests: generic arguments distribute to their nesting level (Outer{A}.Inner{B}), op_CheckedExplicit carries the ~ReturnType suffix like the other conversion operators, and custom modifiers are ignored like Roslyn ignores them (a virtual method's 'in' parameter is modreq(InAttribute) but documented as T@). Array shapes use the spec's lowerbound:size notation, covered by a hand-built module, since C# cannot express non-default array bounds in signatures. Assisted-by: Claude:claude-fable-5:Claude Code	2 months ago
Siegfried Pammer	eac6c59a43	Add unit tests for the XmlDoc ID-string subsystem The Documentation namespace (XmlDocumentationProvider, IdStringProvider, XmlDocLoader) had no test coverage at all, even though XmlDoc is listed as an implemented C# 1 feature on the wiki Language-Feature-Roadmap. These tests pin ID-string generation and FindEntity round-trips for the intricate encodings (nested generic types, `0/``0 type-parameter references, ref/out @ suffixes, pointer and jagged/multi-dimensional array forms incl. [0:,0:], conversion operators with the ~ReturnType suffix, indexers, #ctor) plus XmlDocumentationProvider lookup by ID string and by entity against a generated doc file. All green. Assisted-by: Claude:claude-fable-5:Claude Code	2 months ago

Author

SHA1

Message

Date

Siegfried Pammer

fe147ce211

Port IdStringProvider.GetIdString to SRM

Generate ID strings directly from metadata instead of the type system,
so callers holding only a MetadataFile and an EntityHandle do not need
to materialize a compilation first, and raw metadata names survive
verbatim. GetIdString(IEntity) stays as a thin wrapper over the new
implementation, keeping the published entity-based entry point intact.

The implementation is validated by a differential suite comparing every
symbol of a test corpus against Roslyn's GetDocumentationCommentId.
Corners pinned by those tests: generic arguments distribute to their
nesting level (Outer{A}.Inner{B}), op_CheckedExplicit carries the
~ReturnType suffix like the other conversion operators, and custom
modifiers are ignored like Roslyn ignores them (a virtual method's 'in'
parameter is modreq(InAttribute) but documented as T@). Array shapes
use the spec's lowerbound:size notation, covered by a hand-built
module, since C# cannot express non-default array bounds in signatures.

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

2 months ago

Siegfried Pammer

eac6c59a43

Add unit tests for the XmlDoc ID-string subsystem

The Documentation namespace (XmlDocumentationProvider, IdStringProvider,
XmlDocLoader) had no test coverage at all, even though XmlDoc is listed
as an implemented C# 1 feature on the wiki Language-Feature-Roadmap.
These tests pin ID-string generation and FindEntity round-trips for the
intricate encodings (nested generic types, `0/``0 type-parameter
references, ref/out @ suffixes, pointer and jagged/multi-dimensional
array forms incl. [0:,0:], conversion operators with the ~ReturnType
suffix, indexers, #ctor) plus XmlDocumentationProvider lookup by ID
string and by entity against a generated doc file. All green.

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

2 months ago

2 Commits (fe147ce211b8e2963ff64d299d3ac47ca166a67d)