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.
The whole idea of expressions is very nice, and I can’t imagine using ternary expressions anywhere after learning Rust.
Also implicit returns ❤️
I never got to like implicit anything.
Not even returns. Ever.
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 dofunction()? It’s shorter, simpler, and I don’t waste keystrokes.