# Query.jl and CUDA

**URL:** https://discourse.julialang.org/t/query-jl-and-cuda/94205
**Category:** Data
**Created:** [February 7, 2023, 1:07pm UTC](https://discourse.julialang.org/t/query-jl-and-cuda/94205 "2023-02-07T13:07:53Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![hovi](https://avatars.discourse-cdn.com/v4/letter/h/76d3ee/32.png) [@hovi](https://discourse.julialang.org/u/hovi)
#### Post date: [February 7, 2023, 1:07pm UTC](https://discourse.julialang.org/t/query-jl-and-cuda/94205/1 "2023-02-07T13:07:53Z")

</div>

I am playing with Query.jl and it works fine with CPU code, I even measured some usecases and it works faster than using “classic” for loops code.  
What I don’t know is, if it has any support for CUDA or any kind of guidelines as I see the biggest usage in kernel code. Does anyone have experience in using Query.jl in CUDA kernel code?

To be specific, I would like to filter the cycle that goes across the threads, for example something like this:

```julia
for i in index:stride:l |> @filter(_ != some_id)
...

```

Instead of:

```julia
for i in index:stride:l
    if i == some_id
        continue
    end
...

```
