Christoffer Lerno
Christoffer Lerno
Yes, but it doesn't look like that's what it does. More like it's running the compiler without any arguments.
For C and C3 I can only see that "run" runs the compiler.
If the stdlib has the functions, then they must forward to the builtins. The problem is that vectors are generic over type and length. Currently all builtins are "function like"...
So this means adding quite a bit of functionality to the language in order for this to work. And that's certainly a bit of novel design needed.
There's #300 which discusses how the builtins may be written syntactically.
In regards whether they should be dot operations: I don't know. It feels slightly weird to do `1.ctlz()`, but theoretically that could be possible. It's all about what the core...
bitreverse, ctlz, ctpop etc will be standard library functions/macros – which in the llvm case are backed by builtins. This is different from Zig, since Zig's builtins are part of...
I am not sure what you mean. Just to be clear: I am not saying that functions like ctlz aren't useful, nor do I mean they shouldn't be included. Can...
The problem is overloading generic types. Let's say you wanted dot syntax, then something like this would be necessary: ```c fn int[].shuffle(int[]* ...) { ... } ```
@data-man You can use bitreverse, bswap, ctz, clz and popcount using the new `bits` module. Functions work on int vectors and ints.