sdroege/byte-slice-cast

Safely cast slices of one built-in fundamental number type to another

byte-slice-cast

Safely cast between byte slices and slices of another built-in fundamental number type.

LICENSE

byte-slice-cast is licensed under the MIT license (LICENSE or http://opensource.org/licenses/MIT).

Contribution

Any kinds of contributions are welcome as a pull request.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in byte-slice-cast by you shall be licensed under the MIT license as above, without any additional terms or conditions.

byte-slice-cast's Issues

What's keeping this from being 1.0 right now?

This API is the exact API that I was imagining when I went to look for a crate like this. More generic even, which is cool.

The version is only at 0.2, but it's been sitting there for half a year it looks like. Is there something holding it back from being 1.0 or could it be version bumped?

Zero length slice casting

The following conversion fails with the AlignmentMismatch error:

let slice: Vec<u8> = Vec::new();
let converted_slice = slice.as_slice_of::<u16>().unwrap();

It is more a question than an issue: can such conversions be made? It will make writing generic code easier.

Please add support for manually selecting endianness

For example: https://docs.rs/byteorder/latest/byteorder/index.html#types

Support conversion between Box<[u8]>/`Box<[f32]>` (and similarly for Vec)

Would be useful for servo-media so that we can avoid copies at the sink.

Support primitive array

Would you be open to supporting primitive arrays? Since the layout appear to be well defined, it should be safe to do so.

Add support for casting Vec<T> -> Vec<U>

Can be done via Vec::from_raw_parts and would have the same rules as the slice casting. Ideally we can re-use the most of the infrastructure here.

Cannot compile on wasm32-unknown-emscripten target (debug mode)

I'm trying to compile a project that depends on byte-slice-cast to a wasm32-unknown-emscripten target. However, when building in debug mode, I get the following weird error:

Compiling byte-slice-cast v0.3.5
Referencing function in another module!
  call void <badref>(i8* %22), !dbg !149
; ModuleID = 'byte_slice_cast.v1okijvo-cgu.15'
void (i8*)* <badref>
; ModuleID = '
error: could not compile `byte-slice-cast`.

Building in release mode works just fine. Compiling any project that depends on byte-slice-cast (even a simple hello world project that does nothing but has a dependency on it) to that specific target results in this error. Any ideas on why this is happening?

Tuple support

Would you be willing to pull the patch that adds support for tuples? It looks like the code is good to go and it is only a matter of adding impl_trait!((T, T)) for each type and then testing it.

I wouldn't go deep with the size of tuples and only implement pairs which I think is the most common case.