Skip to content

Conversation

ax3l
Copy link
Member

@ax3l ax3l commented May 4, 2023

What would it take to migrate to nanobind?

Pro's

See advertising, all great :)

Love the

  • speed & size
  • separate headers for features
  • non-header-only approach
  • C++17 and newer only
  • faster builds: no LTO needed anymore

Notes / Con's

  • limited official compiler support (Clang, GCC, MSVC), especially no coverage yet for GPU (Nvidia NVCC & NVHPC, AMD ROCm, Intel OneAPI)
  • still many warnings (e.g., Wshadow, Wpedantic) in base lib
  • currently, limited public docs improved :)

What would it take to migrate to nanobind?
@ax3l ax3l mentioned this pull request Aug 31, 2023
@ax3l ax3l force-pushed the development branch 8 times, most recently from 352e4dd to 424c52f Compare November 30, 2023 22:16
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.

1 participant