abdul dakkak

I'm going to close this issue. Please file an issue for the Endianness feature

FYI: A bitcast functions was added https://docs.modular.com/mojo/stdlib/memory/unsafe.html#bitcast-2

There are so many variants of Float8 representation. We need to think about which ones does mojo represents and how to expose the variety. For now, we are removing Float8...

We want to have `__bool__` method since it allows one to write code such as ``` if my_simd_type: something() ``` Also, the scalar types (Uint8, Float32, ...) are aliases to...

The way to do this is by explicitly calling the bool method later ``` struct MyPair: var first: Float32 var second: Float32 # We use 'fn' instead of 'def' here...

The way to do that is by adding SIMD[DType.bool, 1] as an initializer to the Bool type. But, we cannot do that currently because Bool is a builtin type but...

This ``` from algorithm import vectorize alias simd_width = 8 fn main(): var size = 16 var ptr = DTypePointer[DType.int64].alloc(size) for i in range(size): ptr[i] = i # move function...

Thanks for reporting. One question is handling the negative power on integral values.

Thanks @tairov for requesting this (in the the live stream of all places :) ) . We'll make sure this is prioritized. Keep up the great work

Makes sense, although users should not be working directly with the bytes within a string :) Also, we try to match C semantics here which uses `char *` for strings...