Skip to content

Remove uniffi_bindgen::backend module. #2495

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mhammond
Copy link
Member

Towards splitting bindings into their own crates. If we are happy to accept binding generation panicing on invalid literals we can remove some low-value code.

A breaking change :( I'll keep it draft until something else forces one :)

Towards splitting bindings into their own crates. If we are happy to
accept binding generation panicing on invalid literals we can remove
some low-value code.
@mhammond mhammond marked this pull request as ready for review April 26, 2025 01:16
@mhammond mhammond requested a review from a team as a code owner April 26, 2025 01:16
@mhammond mhammond requested review from gruberb and removed request for a team April 26, 2025 01:16
Copy link
Contributor

@bendk bendk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I kind of liked the to_askama_error function. It's not that big of a deal, but I'd rather return an error than panic if possible. OTOH, I do think the backend module feels a bit weird. What if this was moved to something like a util or error_util module? That feels a bit more light-weight.

Stepping out -- I figured that when bindings are split out into their own crates, they would still have a dependency on uniffi_bindgen and uniffi_bindgen would still be a place for shared code between all the bindings. Did you have something else in mind?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants