Skip to content

Provide more direct mutable access to shape, strides, and owned Vec #429

Open

Description

@jturner314

It would useful in some cases to have more direct mutable access to the shape, strides, and data representation. This could be resolved with setters that perform safety checks instead of just providing &mut references to the fields themselves. See #425, in particular this comment for some ideas. This does warrant some more discussion, so I'm creating this issue.

Activity

  1. bluss commented on Mar 20, 2018

    @bluss
    Member

    Vec -> We have a hard time exposing a Vec by reference. Ideally we should be able to use our own allocator (let's imagine one where we could request a 64-byte alignment for the data, or something like that).

    Sounds good. With strides we have the issue of moving to the more type correct isize values for strides. (What we have today is isize values stored in usize memory.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions