Dear community:

This is a call for vote to release apache-tvm-ffi version v0.1.14. The
main highlights of this release are

* Structural transformation APIs — StructuralMutator recursively
transforms reflected object graphs, with structural_map providing a
typed callback interface for compiler passes, alongside
maybe_inplace_mutate and var_remap. This completes the structural
family next to the existing equality, hashing, and walking APIs.
* Opaque pointer handler map — third-party extension types that cannot
define or accept monkey-patching of __tvm_ffi_opaque_ptr__ can now
participate in opaque-pointer conversion via
tvm_ffi.core._OPAQUE_PTR_HANDLERS, without changing their owning
package.
* Stronger static typing through Any — static object type bounds are
now propagated across ObjectPtr, ObjectRef, and raw-object conversions
into Any and AnyView, while runtime validation for unconstrained
values is unchanged.
* Rust structural and object binding support — all four structural
operations (walk, visit, map, mutate) gain typed callbacks and a
#[dispatch(...)] frontend; the object binding runtime adds zero-copy
upcasts, identity comparison, and reflection-table method lookup; and
containers now hold heterogeneous Any elements.
* Correctness fixes — Python annotation metadata is stabilized across
versions, and ffi.Error is now picklable so FFI-originated exceptions
survive round-tripping.

Link to draft release notes:
https://github.com/apache/tvm-ffi/releases/tag/v0.1.14-rc0

Link to release candidate:
https://dist.apache.org/repos/dist/dev/tvm/tvm-ffi-v0.1.14-rc0/

Everyone is welcomed to vote. Please vote by replying to this thread
explicitly. The vote will last at least 72 hours, please vote

+1 = approve
+0 = no opinion
-1 = disapprove (provide reason)

NOTE: this thread is being mirrored in GitHub issue
https://github.com/apache/tvm-ffi/issues/726

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to