[apache/tvm-ffi] [VOTE] Release Apache TVM FFI v0.1.14-rc2 (Issue #735)

[Yaxing Cai <no...@github.com>]

cyx-6 created an issue (apache/tvm-ffi#735)

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. C++ `StructuralMap` callbacks accept flexible return types: a replacement value, `Expected<T>`, `Error`/`Unexpected`, or a thrown `Error`, and match before recursive descent so unmatched nodes skip remap lookup and callback-chain work.
* 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.
* Safer copy-on-write through `unique()` — `Object::unique()` now requires one strong reference *and* no external weak references, since a live `WeakObjectPtr` can still upgrade while a strong owner exists. `use_count()` keeps its strong-only semantics.
* Free-threaded Python cross-builds — Python discovery now separates the host interpreter running Cython from the target development artifacts, unblocking 3.14t wheel builds on cross-compiled platforms such as Linux PPC64LE and macOS ARM64.
* 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-rc2

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

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 dev@


-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-ffi/issues/735
You are receiving this because you are subscribed to this thread.

Message ID: <ap...@github.com>

Re: [apache/tvm-ffi] [VOTE] Release Apache TVM FFI v0.1.14-rc2 (Issue #735)

[Yaxing Cai <no...@github.com>]

cyx-6 left a comment (apache/tvm-ffi#735)

Closing this vote — v0.1.14-rc3 supersedes rc2.

rc3 carries 30 commits on top of rc2, including a Rust stubgen backend (#738, #740, #755), a callback-driven `StructuralVisit`/`StructuralMutate` refactor (#750, #751), a batch of inlining and hot-path performance work, and Windows backtrace thread-safety fixes (#754, #763).

@yongwww @MasterJH5574 @tlopex — thank you for the +1s here. We'll validate rc3 downstream before opening the next vote thread, so nothing further is needed for now.

The `c_api.h` C ABI remains byte-for-byte identical to v0.1.13.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-ffi/issues/735#issuecomment-5582435742
You are receiving this because you are subscribed to this thread.

Message ID: <ap...@github.com>

Re: [apache/tvm-ffi] [VOTE] Release Apache TVM FFI v0.1.14-rc2 (Issue #735)

[Yaxing Cai <no...@github.com>]

Closed #735 as completed.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-ffi/issues/735#event-30743140045
You are receiving this because you are subscribed to this thread.

Message ID: <ap...@github.com>

Re: [apache/tvm-ffi] [VOTE] Release Apache TVM FFI v0.1.14-rc2 (Issue #735)

[Yong Wu <no...@github.com>]

yongwww left a comment (apache/tvm-ffi#735)

+1

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-ffi/issues/735#issuecomment-5529822136
You are receiving this because you are subscribed to this thread.

Message ID: <ap...@github.com>

Re: [apache/tvm-ffi] [VOTE] Release Apache TVM FFI v0.1.14-rc2 (Issue #735)

[Shushi Hong <no...@github.com>]

tlopex left a comment (apache/tvm-ffi#735)

+1

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-ffi/issues/735#issuecomment-5548510381
You are receiving this because you are subscribed to this thread.

Message ID: <ap...@github.com>

Re: [apache/tvm-ffi] [VOTE] Release Apache TVM FFI v0.1.14-rc2 (Issue #735)

[Ruihang Lai <no...@github.com>]

MasterJH5574 left a comment (apache/tvm-ffi#735)

+1

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-ffi/issues/735#issuecomment-5530079586
You are receiving this because you are subscribed to this thread.

Message ID: <ap...@github.com>