repr is generally assumed to be side effect free and cheap to run, so things like debuggers tend to show repr of things in scope, including possibly exit
also then it behaves differently between repl and script, since repr never gets run. to do it properly it has to be a new repl keyword I imagine, but I still don't know if I'm sold on the idea
yeah fair enough. that wasn't really my point and I wasn't paying attention
~~yeah it's incorrect bc it destroys multibyte characters, but~~ no idea what you're saying about u8 being a different type from unicode. the original code was reading bytes and converting them too? the typing isn't the issue, you can still store utf8 as a series of bytes
I mean, I'm not a big fan of bash, the most likely default shell, so my advice would be to explore some alternate shells.
I am a little surprised completions aren't working in bash by default, but yeah idk if it's possible to get the cycling through suggestions. double tap tab and it should at least list the options though.
I'd recommend you hop between some shells and see what you like. most distros tend to keep the default shell pretty vanilla, the most change you'll get is maybe zsh with some nicer defauls.
nushell is great and would be my first recommendation. everything is structured like powershell, but way less verbose and more emphasis on integrating the existing cli ecosystem than pwsh's commandlets for everything.
fish or oh-my-zsh are things other people recommend. you don't get structured data but they do give a better completion experience and other nice things
I want to like xonsh, and used it for a few years, but it has the same problems pwsh has with separate ecosystems of structured commands and unstructured text. if you're a python person though I'd consider it too though.
python isn't the only language to do "execute everything imported from a particular file and all top level statements get run". both node and c# (but with restrictions on where top level statements can be) can do that type of thing, I'm sure there's more.
python conventions are unique because they attempt to make their entrypoint also importable itself without side effects. almost no one needs to do that, and I imagine the convention leaked out from the few people that did since it doesn't hurt either.
for instance in node this is the equivalent, even though I've never seen someone try before:
if (path.resolve(url.fileURLToPath(import.meta.url)).includes(path.resolve(process.argv[1])))
{
// main things
}
there are other shells that have all the nice powershell things without the weird stuff (at least for not windows people), like nushell
although I wouldn't be surprised if powershell was the thing that started the trend of better shells
are they switching to Teams or Teams?
ones that can run cli tools do great, they just use npm
because with things that the compiler does, like padding for alignment, it frequently takes up more space than that. that was my argument the whole time. what til are you talking about? I'm talking about an extra layer you've decided doesn't count. ofc sizeof bool will be a byte in all of those languages.
a bool taking up a single byte is a fantasy that those languages use because developers generally don't need to think about all the other stuff going on.
for some people it's nice to start from nothing and build up config, I'd recommend doom for anyone else. it's nice to be given a file with all the settings you can change instead of having to do it all yourself.
a bool is actually a single bit, the rest is all padding
I'm sure all of them are just cherrypicked hotfixes from main tho