So that we can simplify some code and simplify the implmentation
when we want to add new features (like adding new bang operators).
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/TableGen/TGLexer.h | ||
---|---|---|
88 | Why are Bit to TrueKW excluded from classification? If they cannot be clustered together, I think it would make sense to move them down to the bottom of the struct, so that that the closing of a group with *LAST would be followed directly by a *START of a new group. |
This LGTM, thanks.
I have noticed that the "unclustered" values are still not grouped together. I thought it was a matter of just the few I mentioned in my first comment but apparently there are more.
I would have ordered the enum as { unclustered, group1, group2, ....}, just because it would have make it easier to find the cluster. But this is really debatable as it is my personal preference, no need to change it if you do not want to.
Thanks!
Francesco
llvm/lib/TableGen/TGLexer.h | ||
---|---|---|
157–158 | same for these? Move them to the "unclustered" section? | |
165–166 | same, move them to the unclustered section? |
Why are Bit to TrueKW excluded from classification? If they cannot be clustered together, I think it would make sense to move them down to the bottom of the struct, so that that the closing of a group with *LAST would be followed directly by a *START of a new group.