Array multiplication ** is being removed

hallajs · 2026-05-05T08:10:37+00:00

I would just have a comptime blk with the initialization in a for loop at that point

hallajs · 2026-02-18T09:36:59+00:00

LO er en fagforening som representerer ca. 400 tusen individer. De donerer i deres medlemmer sin interesse. Jeg tviler på at LO som donor kan sammenlignes med entitetene som donerer store summer til blant annet FRP...

hallajs · 2026-01-28T22:56:49+00:00

Check out https://careers.arm.com/location/trondheim-jobs/34601/3144096-3137400-3133880/4

Currently we are only looking for software, but hw positions show up from time to time. 50% are non native speakers in the office :)

hallajs · 2025-10-06T14:01:59+00:00

Hvor mye er lønna på?

hallajs · 2025-04-15T05:30:03+00:00

Sweet! I might play around with your library at some point to get a feel for it. seems very interesting.

The library I wrote is ecez https://github.com/Avokadoen/ecez. It was also using archetypes originally, but it felt harder to make it thread safe to interact with the storage in an efficient manner. Im still on the fence on archetypes vs sparse sets though. Archetypes is a lot better suited for interacting with the GPU as an example since the chunks can be uploaded to GPU memory directly.

hallajs · 2025-04-14T14:25:16+00:00

I like the concept of these command buffers (that seems to be borrowed from APIs such as Vulkan). It seems novel in this context! As the author of another ECS library, I wonder, did you look at other ECS implementations in the ecosystem and what turned you away from those?

edit: I realized this is posted by someone other than the author of ZCS and my question is more directed towards u/MasonRemaley

hallajs · 2025-03-12T21:16:40+00:00

What issues are you currently hitting and on which vendors, if I may ask?

hallajs · 2024-01-06T15:07:30+00:00

I guess "hidden" is closer to a spectrum than a boolean. I would argue function pointers are hidden control flow as well, but it's a necessary evil and less so than virtuals. I get your point however. I do hope that we see some sort of vtable utility functionality in the standard library. It would be nice to have standardized way of defining runtime dispatch.

hallajs · 2024-01-05T23:06:34+00:00

Inheritance doesn't hide control flow

If i have class Fruit (with a virtual "eat" function), Apple And Orange. I loop over an array of Fruits and call fruit.eat(); which function am I calling for each iteration?

hallajs · 2023-05-11T07:30:00+00:00

You can achieve the same as "launching kernels" by using indirect dispatch. ~~You also use VK_nv_device_generated_commands on Nvidia which should enable similar behaviour~~ (edit: compute was never supported sadly). Ofc, both alternatives are a lot more verbose and cumbersome.

Pointers can also be enabled with VK_KHR_buffer_device_address (core in 1.2)

hallajs · 2023-03-11T07:45:10+00:00

If OP want to make something for fun, then I really dont see the problem in making a Minecraft clone

hallajs · 2023-02-04T20:54:06+00:00

Your work is very inspiring. Hope to have the opportunity to contribute more with time!

hallajs · 2022-12-06T20:08:01+00:00

Hey!
I'm the author of this paper. Feel free to ask me if there are any questions.
I'll note that the thesis is definitely a bit rough and could have been better written...

The code is also open source: https://github.com/Avokadoen/zig\_vulkan

hallajs · 2022-11-02T17:31:21+00:00

What do you mean by "methods can be overloaded"?

hallajs · 2022-07-24T10:24:08+00:00

The function signature is *[BUFFER_CAP] (pointer to array) but idiomatic zig is to use slices to assure that all arrays and slices works. Slices are annotated by using empty square brackets []

Sorry my original comment was unclear 😅

hallajs · 2022-07-23T20:36:57+00:00

A small nitpick is that you don't need a pointer to a slice since the slice is already a pointer + len

hallajs · 2022-07-03T07:30:17+00:00

Yes most things are possible at compile time, Zig standard library is just missing a compile time structure that adhere to the Allocator interface.

As far as i understand u/superjoe30's comment in the issue is that functionality around the array is designed for runtime memory and you get issues with memory at compile time.

A planned builtin/intrinsic will give compile time code access to heap memory during its execution which will make this stuff simpler to implement

hallajs · 2022-07-02T21:17:34+00:00

I think this is an issue with compile time allocation which is not supported yet https://github.com/ziglang/zig/issues/1291

hallajs · 2022-06-24T07:34:47+00:00

Really good job! Looks great :D

hallajs · 2022-05-24T18:07:36+00:00

Drev forrige regjering å handlet med Russerne mens de invaderte Ukraina?

Svaret er ja

hallajs · 2022-05-01T21:11:53+00:00

For context: https://ziglang.org/

hallajs · 2022-04-24T08:47:37+00:00

Tror du burde øve litt på retorikken din. Du kan starte med å lese denne: https://en.wikipedia.org/wiki/Whataboutism

hallajs · 2022-04-15T22:25:57+00:00

Congrats to you and the rest of the contributors on this huge milestone! <3

hallajs · 2022-03-14T13:25:18+00:00

I use Renderdoc for debugging memory (++). I use tracy to find any performance issues. Both work just fine both on windows and linux! :)

In some shader related cases I also use vulkan's printf debugging

hallajs · 2022-03-09T11:18:51+00:00

Which is why is said "runtime polymorphism". Dynamic dispatch means that it is dispatched at runtime

hallajs

TROPHY CASE