[main] optparse: add support for prefix flags#20923
Closed
silverweed wants to merge 1 commit into
Closed
Conversation
Contributor
|
I feel like this approach is a bit too limiting. If you have a short-flag starting with a certain character, you can't define any other option that starts with the same character. In LLVM, they have a specific argument you can pass when creating a prefix option, something like: Could we support something similar? For example: |
Test Results 11 files 11 suites 1d 6h 17m 38s ⏱️ Results for commit 2f2f38e. |
Contributor
Author
|
@devajithvs see #20947 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
TL;DR: adds support for treating
-Dfooas-D foo. See header documentation for details.EDIT: superseded by #20947
Checklist: