[C#] Adding RawModuleDefV10 to C# Module Bindings
#4262
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Changes
Moduleso all V10 builder state and registration helpers now live onpartial class RawModuleDefV10. The staticModuleclass simply registers components against that builder and serializes viamoduleDef.BuildModuleDefinition()__describe_module__export. Only__describe_module_v10__is emitted now across the runtime, native shim, generated bindings, and snapshotsAPI and ABI breaking changes
Modules built with these bindings now expose only
__describe_module_v10__The legacy
__describe_module__symbol is gone from both managed and native layers. Hosts expecting the old export must switch to the V10 entry point (which is already the canonical ABI for 2.0).Expected complexity level and risk
2 - Low. The refactor keeps the previous builder logic but relocates it, and the export removal matches the already-supported V10 host path.
Testing
dotnet build crates/bindings-csharp/Runtime/Runtime.csprojwithout errors.dotnet test crates/bindings-csharp/Codegen.Tests/Codegen.Tests.csprojwithout errors.bash run-regression-tests.shwithout errors.