Skip to content
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

Auto await feature #186

Merged
merged 14 commits into from Mar 19, 2023
Merged

Auto await feature #186

merged 14 commits into from Mar 19, 2023

Conversation

la10736
Copy link
Owner

@la10736 la10736 commented Mar 19, 2023

This replace #170 PR and fix #157
I did some refactoring to remove some craps introduce with #[future] feature

boilerplate in the rendering stage. Just render
and test (missing the parse stage).
`fixture` and moved the parsing code in
`extend_with_function_attrs` trait impl
that're already tested in future module
the old impl. Also recoverd tests for
errors but implemented them in future
module
pass arguments info down to the
renderers and impleneted all tests
in render code to check that the
parsed info will used correctly.
method because we want the future in the
signature. Now E2E tests for fixture are
enabled and work.
@la10736 la10736 merged commit 91c60bd into master Mar 19, 2023
1 check passed
@la10736 la10736 deleted the auto_await branch March 19, 2023 09:53
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.

Is there an alternative to this .await syntax?
1 participant