101·
2 years agoThe whole idea of expressions is very nice, and I can’t imagine using ternary expressions anywhere after learning Rust.
Also implicit returns ❤️
Oro [she/they]
Queer individual from southeast Texas. Helping to work on the Linux desktop - currently contributing to Flatpak and Flathub, getting familiar with GNOME.
Can find me at:
https://orowith2os.gitlab.io/ https://tech.lgbt/@orowith2os https://github.com/orowith2os/ https://gitlab.com/OroWith2Os/
- 0 Posts
- 2 Comments
Joined 2 years ago
Cake day: July 8th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
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.