arrayfire-rust v3.6.0 Release Notes

Release Date: 2018-09-27 // over 5 years ago
  • ๐Ÿ†• New Features & Improvements

    Functions

    ๐Ÿ’ฅ Breaking Changes

    Prior to v3.6.0 Array structure was a non-generic structure that didn't carry any information about the type of data being managed by the ArrayFire's memory manager. From now on, Array is generic over the type of data it is storing, thus has all the benefits of Rust checks. This may result in few code changes on the user's side. Hopefully they are minimal. Please don't hesitate to contact if you face any issue while moving to 3.6.0. We have made the necessary modifications to the examples provided in the crate to give you an idea of what the changes might look like. We will keep improving the API based on community feedback.

    ๐Ÿ‘Œ Improvements

    • Array is a generic and hence comes with all the checks rust carries out. Hopefully, this helps the users in avoiding type related issues.
    • All sub-modules are organized into domain based categories so that they can be compiled individually into a crate with only the required functionality. Core is the only mandatory module needed by any other module.

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fix Rust enum representations to match FFI ABI.
    • ๐Ÿ›  Fix a couple of typos in the documentation.

    Community contributors

    Thank you.

    ๐Ÿš€ For more information about the performance and bug fixes made in the upstream, ArrayFire, please refer to the following two release notes.