-
**Description**
The HLSL syntax documentation for `WaveActiveBitAnd` (as well as `Or` and `Xor`) is:
```
WaveActiveBitAnd(
expr
);
```
https://learn.microsoft.com/en-us/windows/win32/d…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Environment
```markdown
- Milvus version:master-20240906-9871841f
- Deployment mode(standalone or cluster):
…
-
This is an issue with the current API design I've come to feel by using the API more, by thinking about it more, and through some user feedback (/cc @slimsag).
Right now, `githubql` defines a custo…
-
After upgrading to v19 (to align with Prisma 5), we are experiencing issues with our existing graphql queries and query generation.
Our generated types have changed, specifically in the xxxOrderByW…
-
For example, if I use the well-known LatLng type in a REST API, it should work. Presently the type has no fields so I can't leverage that type's shape outside of proto contexts.
-
When converting Java scalar types through JPype into numpy types, the behaviour isn't quite as nice as it is for array types. For example the following cases are a bit surprising:
```
import jpype…
-
See the comments on [reddit](https://www.reddit.com/r/rust/comments/6tw57q/nalgebra_v013_released_with_purerust_svd_lu_etc/dlp0fw4/).
-
The spec makes no statement about what GraphQL input values are valid for a custom `Scalar` value.
-------
Let's take an `IntRange` type for example:
- It always has exactly two `Int!` values: …
-
Related to #43
- [x] Support to `is_int()`, `is_float()`, `is_string()`, `is_bool()`, `is_null()`, `is_object()`, `is_scalar()` and aliases;
- [ ] Support to `is_array()`, `is_countable()` and `i…
-
### Search before asking
- [X] I had searched in the [issues](https://github.com/datafuselabs/databend/issues) and found no similar issues.
### Version
v1.2.314-nightly
### What's Wr…