Exactly. It's a small quality-of-life feature to avoid the repetitive mkdir && cd sequence. In GRSH, it also ensures the directory is created with the necessary permissions before the shell attempts to switch into it.
Great question! While you could technically hack a similar behavior using a shell function (not a simple alias, as aliases don't handle positional arguments well), grsh implements mkcd as a native builtin.
By baking it into the shell in Rust, I can ensure atomic execution and better error handling without relying on the user's specific .bashrc or .zshrc hacks. It's about providing a 'batteries-included' experience where common workflows are first-class citizens of the shell itself.
That's a nice thing, but I have a few remarks/questions.
"the International Astronomical Union adopted a broad framework calling for the moon to have its own time reference."
I wonder how the "01/01/1970 00:00:00"-for-the-moon will be decided. I hope also there won't be
Also, and even if apparently the moon won't be considered as a supplementary set of timezones (thank god no [0]), there will have to be a kind of correspondence with the earth GMT/UTC. And will there have to be a lunar calendar ? There are not so many days in a terrestrial year than on the moon IIRC.I don't quite get the whole picture, but it's interesting.
Why not Alt-x like emacs (should I say Meta-x) ?
I'm a big user of sublime text and I find alt-x way more convenient simply because it's very easy to do that shortcut with one hand. Plus the slot is not used by default config.
I'm sorry, but having a quick glance to the syntax I could not get why you added another symbol in the boolean operators... Isn't it supposed to be a modern syntax ?
This feels old and clunky
Are you talking about quantum boolean logical operators? && is for boolean, and & will be for single bit, &&& is for quantum booleans, such as qtrue &&& both = both. the logic operators with 3 symbols are qbool, !! is for qbool, and ^^ is qbool xor, then && || ! == != are bool, and & | will be bitwise logic for singular bits.
Except for the name in itself, nowhere in the features it is explicit that the language does quantum computation, in addition to traditional computation.
& is used, so && is boolean (ofcourse almost all languages use && for and), and &&& is for quantum boolean which has 4 states, because & and && are used. Should i clarify this more in the syntax demo file and the readme and docs?
reply