Alexandre A. Bizri
Alexandre A. Bizri
First of all, congrats and thanks for the crate ! I'm currently using `fasteval` in a computer graphics project, and in that world, `f64` or double-precision numbers are very rarely...
Currently, there is no way to efficiently use `ocl` without `unsafe` everywhere, (not only on kernel execution, but also on buffer creation, mem-mapping, ...), and for good reason: as they...
Recently, `mem::uninitialized`, which has always been very UB-prone to use, has been replaced with `mem::MaybeUninit`. This PR replaces every use of the former by the latter, though it isn't a...
Replace the `r#try!` macro by the `?` operator, which now has been in stable rust for quite some time.
Types implementing `OclPrm` should not only have the same layout as in `C` via `#[repr(C)]` but also be valid in any bit configuration of the underlying binary representation. That means,...
When creating a `ProQue` for example, and making it go out of scope (and be dropped), the `Context` referred to by `Queue` or `Program` is dropped, making calls like `Queue::context()`...
This PR adds feature-gated support for rust's new(ish) allocator api on `Vec` (see https://github.com/rust-lang/rust/issues/32838 & https://doc.rust-lang.org/unstable-book/library-features/allocator-api.html). This enables support for custom allocators, which are often needed in video games &...
As suggested by @kilograham (in https://github.com/raspberrypi/pico-sdk/issues/1929#issuecomment-2364746391), add `pico_runtime_init` as well as `pico_runtime` and `boot_picobin_headers` to the `CMakeLists.txt`s defining `hardware_irq` and `pico_bootrom_headers`. While the issue initially was reported only for `hardware_irq`...
Until now they were not implemented, even though they are in rust nightly's `core::simd`. Besides creating an arbitrary limitation, this practically makes it more complicated & ugly to have lane-count...