You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Has a complete port of rd-kit been considered? any ideas of scope involved? given your experiences with rdkit-rs, would you recommend doing it? it's unlikely, but I might give this a try and thought to ask.
Edit: considering the scope, it would just some part (which is also better given that RDKit is super monolithic), also here any opinions on what would make sense maybe?
The scope decision is now documented in #57 and its binding audit: this project wraps native RDKit through CXX and focuses on a coherent molecule/atom/bond/conformer and chemistry-workflow surface. The inventory measures this repository's bindings, not a percentage of every upstream API. A Rust reimplementation of RDKit chemistry would be a separate project with its own behavioral validation; it is not part of this modernization. Closing this scope question as answered, without claiming a complete port.
Activity
xrl commentedon Oct 9, 2026
The scope decision is now documented in #57 and its binding audit: this project wraps native RDKit through CXX and focuses on a coherent molecule/atom/bond/conformer and chemistry-workflow surface. The inventory measures this repository's bindings, not a percentage of every upstream API. A Rust reimplementation of RDKit chemistry would be a separate project with its own behavioral validation; it is not part of this modernization. Closing this scope question as answered, without claiming a complete port.