Advice on transition from Yoga (C++)

[Hexlord]

Could someone please provide advice on following questions:

1. For past users of Yoga C++ api, is there a way to wrap Taffy to behave similarly (a C++ accessible struct withing a node with its style properties and a function to mark a node dirty)? What would be the best approach?

2. Are you aware of any other flex-box similar layout engines that are in C/C++ or are feasible to rewrite in C/C++? The goal is to have similar behavior (defining dimensions, paddings, layout direction, wrapping) without the many issues the Yoga has (terrible performance with auto dimensions, subpar performance in general - probably due to recursive nature of feedback-type constraints that might not be actually needed in our use-cases, inconsistent jittery position and dimension rounding).

[nicoburns]

I do have a PR with some unfinished C bindings for Taffy (#404). If you're willing to add support for building Rust to your build system (which should be quite straightforward for a library like Taffy that doesn't have any complex dependencies - cargo build will produce you a static library) then my strong recommendation would be to help us finish those bindings. We would be willing to take on ongoing maintenance of these bindings as part of the Taffy project.

Alternatively, there is actually a C++ port of Taffy (https://github.com/inobelar/taffy_cpp). However, it's from ~2 years ago and is unmaintained so if you go that route then you'd probably be maintaining the port yourself.