Skip to content

Fix issue with async and locally abstract types #5982

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 6, 2023

Conversation

cristianoc
Copy link
Collaborator

@cristianoc cristianoc commented Feb 5, 2023

To fix the printer, the async internal representation via an attribute needs to be preserved on functions starting with a locally abstract type. For this reason, annotations cannot be placed individually on the first locally abstract type, if that's how the function starts. Some printer tests of functions starting with an abstract type have changed because of this.

Fixes #5974

To fix the printer, the async internal representation via an attribute needs to be preserved on functions starting with a locally abstract type.
For this reason, annotations cannot be placed individually on the first locally abstract type, if that's how the function starts.

Fixes #5974
@cristianoc cristianoc force-pushed the async_locally_abstract branch from d5cc12a to db07632 Compare February 6, 2023 09:41
cristianoc added a commit that referenced this pull request Feb 6, 2023
This is a port of the compiler part of #5982 to 10.1.
@cristianoc cristianoc merged commit 870db32 into master Feb 6, 2023
@cristianoc cristianoc deleted the async_locally_abstract branch February 6, 2023 11:02
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.

async function containing locally abstract type is not considered an async context
1 participant