![](https://beehaw.org/pictrs/image/93659d94-5df3-4b88-b59f-4f521c9b80e4.webp)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
Doing everything explicitly can get to be annoying, especially when it comes to what you had to do before without Vulkan’s VK_EXT_shader_object.
It’s clear that some stuff should be implicit - most types in programming languages, for example; needing to specify a struct type and then the struct itself can be annoying - and other stuff explicit, like low level operations.
Returns are something that usually fall into that “implicit” category. Why should I do let a = function(); return a;
when I can just do function()
? It’s shorter, simpler, and I don’t waste keystrokes.
Considering the amount of downtime I’ve seen with any somewhat large lemmy instance, I don’t think that theory holds up