[CIR] Remove also the !cir.void return type from the textual IR #1249
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.
This is the second phase of #1203, as the first phase has demonstrated that fixing the IR to avoid breaking an MLIR invariant can work.
Now, to avoid adding a new feature in the MLIR parser infrastructure, we change the way CIR IR textual representation is done by removing also
!void
or!cir.void
in the function return types to just follow the normal way the other dialects work to represent function types.See #1203 (comment) for more context.