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

Extern rust fun type checking #1168

Merged
merged 3 commits into from
Oct 20, 2022
Merged

Extern rust fun type checking #1168

merged 3 commits into from
Oct 20, 2022

Conversation

adetaylor
Copy link
Collaborator

Relates to #1166.

Just a mechanical rename, no other changes.

This is because in a future commit we will start to identify some errors
that emanate from Rust code and we want to treat them differently, as we
can attach span information to them.
@adetaylor adetaylor force-pushed the extern_rust_fun_type_checking branch from 0f19773 to 50845c0 Compare October 20, 2022 13:34
Previously extern_rust_function support was highly basic and
didn't usually work at all. This change improevs matters:

* it allows us to emit errors with miette diagnostics from
  this part of the codebase, giving spans in case of trouble
* it validates that the parameters to such a function are
  valid to be used by cxx, as is the return type
* it detects types used as parameters and return type and
  ensures they are not garbage collected elsewhere in autocxx
* it adds a code example.
* we remove a field from RustFun which we didn't actually need
  and replace it with a simple Boolean.

Builds on test case from #1166 (thanks!) and there's a bit of
discussion in #1167.
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.

None yet

2 participants