Since no one has said it yet, please always use <a href="https://www.shellcheck.net/" rel="nofollow">https://www.shellcheck.net/</a> on your scripts, you don't want to be That Guy <a href="https://github.com/ValveSoftware/steam-for-linux/issues/3671" rel="nofollow">https://github.com/ValveSoftware/steam-for-linux/issues/3671</a>
This looks pretty cool!<p>I can't ever imagine using it tho :) If my bash scripts are so complex or critical that I feel the need to type check, I will probably use another scripting language where I can do that more easily while still having readable code.
> the builtin types are:<p>> [...]<p>> boolean: a shortcut for returning a number (as numbers are booleans).<p>Can someone explain? I can understand booleans being numbers (e.g. #define TRUE 1 in C), but how are numbers booleans in bash?
I used to somehow think Bash scripts were ideal given that they were fairly transparent, but I'll take a Go app or Rust program anyday now over something written in shell script. shfmt is an example.
>It is also a very cursed idea taken way too far, and I do not apologize for it<p>Agreed XD<p>It's a really nice idea but I cannot ever see myself writing bash like this