akern40

Thanks! While it's true that methods have new homes, the deref structure means that most things are callable from `ArrayBase`. The exception there is methods that have been re-homed to...

~I should update the `serde` serialization. We can fold it in here or just do a follow-up PR, but either way we should make sure to include it before the...

> I should double-check that I've added all of those aliases Done! I was missing a few. Also added documentation to `RawRef`, deciding to keep it. By keeping it, we...

> I think that we should treat this change as worthy of the 'breaking-changes' label, unless we have very good evidence it's almost entirely free of existing code breakage. Ya,...

@bluss did you have any final follow-up on this PR? Because this changes the paradigm of writing functions in ndarray, I have been building any additional PRs on top of...

We should reconsider the naming of `LayoutRef` - as I work through a shape/stride/dimensionality redesign, I think that the term `LayoutRef` to refer to a joint package of shape, strides,...

@benkay86 I was doing some thinking about this method not just in the context of concrete types but also in the context of using it in a method. Let's take...

Sorry I should've been a little clearer when I was talking about "erasing" trait bounds. I'm worried about the *output*, not the input. > So, for better or worse, we...

> It can be added to your parity() function as needed  Might be time for me to sleep! Really excellent analysis here. I'm in favor of adding that bound...

I think this is a great design. I want to suggest a slight twist inspired by yours that I think balances between ergonomics for the user and maintenance / fragility...