Details
- Reviewers
rriddle nicolasvasilache
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
the topic is discussed here https://llvm.discourse.group/t/list-of-lists-pass-option/5950/3
mlir/include/mlir/Dialect/Linalg/Utils/Utils.h | ||
---|---|---|
40 | Why can't the input format be [[1,2,3],[3,4],[0,1]]? Why the need for _? |
mlir/include/mlir/Dialect/Linalg/Utils/Utils.h | ||
---|---|---|
40 | Yeah I would prefer your notation. I did not do it in this attempt since ListOption splits the input string at every , . That means the nested lists would be split as well and InnerListOptionParser would get "[[1", "2", "3]", "[3", "4]" ... instead of "1_2_3", "3_4" ... I think having a proper nested angular bracket notation would require a custom ListOfListOption instead of just extending ListOption, which may be the better solution anyways. The parser would then need to match opening and closing angular brackets to identify the nested lists. |
mlir/include/mlir/Dialect/Linalg/Utils/Utils.h | ||
---|---|---|
40 | Hmmm, that is quite annoying. Do you know where in the code this is coming from? We could just look into refactoring this to support what we want, even if we have to diverge from llvm::cl. |
mlir/include/mlir/Dialect/Linalg/Utils/Utils.h | ||
---|---|---|
40 | The CommaSeparateAndAddOccurrence function seems to split the string: |
Why can't the input format be [[1,2,3],[3,4],[0,1]]? Why the need for _?