Skip to content

DRAFT Native AOT support#3633

Draft
marcschier wants to merge 20 commits intomasterfrom
analyzerfixes2
Draft

DRAFT Native AOT support#3633
marcschier wants to merge 20 commits intomasterfrom
analyzerfixes2

Conversation

@marcschier
Copy link
Collaborator

@marcschier marcschier commented Mar 19, 2026

Proposed changes

Add native AOT support using annotations and by replacing more use of untyped and reflection code

Related Issues

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply. You can also fill these out after creating the PR.

  • Bugfix (non-breaking change which fixes an issue)
  • Enhancement (non-breaking change which adds functionality)
  • Test enhancement (non-breaking change to increase test coverage)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected, requires version increase of Nuget packages)
  • Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING doc.
  • I have signed the CLA.
  • I ran tests locally with my changes, all passed.
  • I fixed all failing tests in the CI pipelines.
  • I fixed all introduced issues with CodeQL and LGTM.
  • I have added tests that prove my fix is effective or that my feature works and increased code coverage.
  • I have added necessary documentation (if appropriate).
  • Any dependent changes have been merged and published in downstream modules.

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

marcschier and others added 14 commits March 19, 2026 09:10
Replace Mono.Options OptionSet command-line parsing with System.CommandLine
RootCommand/Option<T>/Argument<T> pattern across all 6 projects:

- ConsoleReferenceServer: Use SetAction with async handler, options defined
  as Option<T> instances, env var merging via MergeEnvironmentArgs
- ConsoleReferenceClient: Same pattern with Argument<string> for server URL
- ConsoleReferenceSubscriber: Inline SetAction handler replaces OptionSet
- ConsoleReferencePublisher: Same pattern as Subscriber
- Fuzz.Tools: Same pattern with playback/testcases/stacktrace options
- MonoReferenceServer: Use centrally managed package version

System.CommandLine provides automatic --help/-h/-? handling, automatic
--version support, and better error messages for invalid arguments.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe you can make the serialization code more accessible for tests, so it does not need to be repeated for the tests?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support Native AOT compilation of applications against stack

2 participants