Misc doc updates

Author: jakobnissen

docs/src/base.md

@@ -39,15 +39,11 @@ MemoryKind could be replaced with a function that returned `nothing`, or the cor
 MemoryView type directly, but it's nicer to dispatch on `::MemoryKind` than on `::Union{Nothing, Type{<:MemoryView}}`.
 
 ## Limitations
-* Currently, `MemoryView` does not make use of `Core.GenericMemory`'s additional parameters, such as
-  atomicity or address space.
-  This may easily be added with a `GenericMemoryView` type, similar to `Memory` / `GenericMemory`.
+* Many optimised fast methods for more established types like `Vector` are missing for `MemoryView`.
+  These are added over time. Please make an issue or a PR as you encounter missing methods.
 
-* I can't figure out how to support reinterpreted arrays.
-  Any way I can think of doing so will significantly complicate `MemoryView`, which takes away some of
-  the appeal of this type's simplicity.
-  It's possible that reinterpreted arrays are so outside Julia's ordinary memory management
-  that this simply can't be done.
+* Currently, `MemoryView` does not make use of `Core.GenericMemory`'s additional parameters, such as atomicity or address space.
+  This may easily be added with a `GenericMemoryView` type, similar to `Memory` / `GenericMemory`.
 
 * Currently, `String`s are not backed by `Memory` in Julia. Therefore, creating a `MemoryView` of a string
   requires heap-allocating a new `Memory` pointing to the existing memory of the string.
@@ -67,7 +63,7 @@ less nicely with the Julia runtime. Also, the existing `GenericMemoryRef` is ess
 #### Advantages
 * Pointer-based memviews are cheaper to construct, and do not allocate for strings, unlike `Memory`.
   Perhaps in the future, strings too will be backed by `Memory`.
-* Their interaction with the GC is simpler (as there is no interaction)
+* Pointer-based memory views allows interoperability with non-Julia memory like C owned structs easier.
 
 #### Disadvantages
 * While some low-level methods using `MemoryView` will just forward to calling external libraries where

docs/src/index.md

@@ -17,13 +17,13 @@ The `MemoryView` type is a useful low-level building block for code that operate
 The `MemoryView` type has the following layout:
 
 ```julia
-struct MemoryView{T, M} <: AbstractVector{T}
+struct MemoryView{T, M} <: DenseVector{T}
     ref::MemoryRef{T},
     len::Int
 end
 ```
 
-The `M` parameter is either `Mutable` or `Immutable`, which are unexported types defined in this package.
+The `M` parameter is either `Mutable` or `Immutable`, which are unexported but public types defined in this package.
 MemoryViews also provide the following aliases for convenience:
 
 ```julia

src/MemoryViews.jl

@@ -3,6 +3,8 @@ module MemoryViews
 export MemoryView,
     ImmutableMemoryView, MutableMemoryView, MemoryKind, IsMemory, NotMemory, inner
 
+public Mutable, Immutable
+
 """
     Unsafe