Provides safe trivial transmutes in generic context, emulating specialization on stable Rust. These functions are designed for being optimized out by the compiler, so are probably zero-cost in most cases.
``rust
fn specialized_function<T: 'static>(x: T) -> String {
// We have an efficient algorithm for
i32and worse algorithm for any other type.
// With
cismute` we can do:
match cismute::owned::
asserteq!(specializedfunction(42i32), "got an i32: 42"); asserteq!(specialized_function(":)"), "got something else"); ```
cismute::owned
works only for 'static
types. If your type is a reference, you should use cismute::reference
or cismute::mutable
.
``rust
fn specialized_function<T: 'static>(x: &T) -> String {
// We have an efficient algorithm for
i32and worse algorithm for any other type.
// With
cismute` we can do:
match cismute::reference::
asserteq!(specializedfunction(&42i32), "got an i32: 42"); asserteq!(specialized_function(&":)"), "got something else"); ```
There’s also a more generic function cismute::value
which can do all three. Writing all type arguments can be cumbersome, so you can also pass the type pair as an argument via cismute::value_with
:
```rust use cismute::Pair;
fn specializedfunction
asserteq!(specializedfunction(&42i32), "got an i32: 42"); asserteq!(specialized_function(&":)"), "got something else"); ```
There are also switch!()
macro and switch()
function to match one value with multiple types.
[refl] and [identity] require providing a proof of type equality to transmute. This is impossible in some contexts (e.g. when implementing a generic method of a foreign trait) and makes zero-cost switching on multiple types really hard if not impossible, since you need to optionally provide proofs for different types.
[safe-transmute] provides various safe transmutations, but doesn’t provide transmutation to the same type.