Ary Borenszweig
Ary Borenszweig
Hi. Not yet, but it's very likely we'll have these in the future
Changed title because Atomics are already implemented
If you want, you can try experimenting with this. The implementation seems similar to the one for StaticArray, but instead of llvm array you must use LLVM vector. Searching for...
Maybe make the primitive methods private and add the check for public methods?
You need to do: ```crystal types["Bool"].types["Vector"] = vec_bool = ... ``` Types contain other types. Like in code.
Or just `bool.types["Vector"] = ...` if `bool` was defined in a previous line.
Though namespacing things like this makes little sense. Probably `IntVector`, `BoolVector`, `FloatVector` is better. In any case, without a concrete use case I don't know why we'd like to eventually...
@malte-v Given that `Int::Vector` and `Float::Vector` have different operations, I can imagine there being `Int::Matrix` and `Float::Matrix` because of the same reason...
Regarding the errors here, I wonder if they should happen exactly where they are. For example: ```noir #[foo] // Currently errors here comptime fn foo(_: FunctionDefinition) -> Quoted { quote...
Reduced: ```noir mod moo { fn foo() {} pub trait Trait { fn bar() { foo() } } } impl moo::Trait for i32 {} ``` It seems the method `bar`,...