You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to support attributes like #[inline(never)] the frontend needs its own InlineType similar to what we have in SSA. Currently we just check whether we have a #[fold] attribute and then that flag determines how we set the InlineType in SSA.
Happy Case
We should be able to compile multiple ACIR functions for a program like such:
# Description
## Problem\*
Resolves#4910
## Summary\*
We add a new attribute `Inline(String)`. Currently we only support one
`InlineType` variant of `Never`. This PR also moves `InlineType` into
the monomorphization ast as its functionality is expected to be shared
across various frontend passes as well as the SSA/ACIR gen.
## Additional Context
I know there is some plans to split the AST off into its own crate as
per (#4852). This change
shouldn't affect make the split much more dififcult as the evaluator
already depends on the AST as the issue mentions and this `InlineType`
is pretty isolated in its usage.
## Documentation\*
Check one:
- [ ] No documentation needed.
- [ ] Documentation included in this PR.
- [X] **[For Experimental Features]** Documentation to be submitted in a
separate PR.
# PR Checklist\*
- [X] I have tested the changes locally.
- [X] I have formatted the changes with [Prettier](https://prettier.io/)
and/or `cargo fmt` on default settings.
---------
Co-authored-by: Tom French <[email protected]>
Problem
In order to support attributes like
#[inline(never)]
the frontend needs its ownInlineType
similar to what we have in SSA. Currently we just check whether we have a#[fold]
attribute and then that flag determines how we set theInlineType
in SSA.Happy Case
We should be able to compile multiple ACIR functions for a program like such:
Project Impact
Blocker
Impact Context
No response
Workaround
None
Workaround Description
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response
The text was updated successfully, but these errors were encountered: