These are pretty much your only two options at the moment.

If Rust ever gets a context system, that could be solved better: https://tmandry.gitlab.io/blog/...

If you know when the interner is no longer used, you could clear it afterwards, avoiding a memory leak while storing it in a global.

That's only a theory in the sense that gravity is a theory

@IntrusionCM How about Meson's wrap system?

https://mesonbuild.com/Wrap-depende...

@IntrusionCM I think it's fair to compare cargo to meson. Both contain a build system and dependency management infrastructure.

But IMO, meson is a lot more flexible and can handle complex cases, like multi-language projects, better.

On the other hand, starting a new rust project is really straightforward, due to cargo's defaults and lack of configurability.

Was about to call bullshit when I read the username. Calling that workplace a hellhole would be be wrong on hell.

@Root when are you getting out?

@iiii right. Preferably filled with something heavy to induce some much-needed common sense.

I've used Latex for my CV a few times.

I started with the komacv class, but I didn't like the layout that much anymore.

So I did my last one in limecv, which IMHO looked better. However, limecv leaves the entry formatting completely up to the user, which is nice if you want the flexibility but takes some time and may be harder for beginners.

There is also Awesome CV (https://github.com/posquit0/...) but I haven't tried that one yet.

If you decide against Latex, there is also https://rxresu.me/, which is open-source if you care about that.

@nowaho, thanks for the clarification!

I think there is some kind of open option you have to pass for constraints to be checked.

But I might misremember that

My therapist told me, “Don’t listen to the voices telling you to hold back, focus on the ones telling you to burn them all.”

Or was it the other way, round? I keep forgetting. But I like it better this way.

It's called survivorship bias and I think it is very common with founders.

What's an untyped language?

It's called a call center for a reason.

Also, email often has the same problem as a call: The person receiving it drops everything to check their inbox when they get the notification.

@Hazarth But how if I can't save my changes to zshenv?

It seems that way.

@user00015 if you have an automated code formatter, it should be easy enough and acts as a brown M&M check. That part I find reasonable enough.

However, I'm put off by the apparent lack of automation. Code formatting is easy enough to check in CI. Or in a pre-commit hook for that matter. It should never be necessary to bring that up in a code review.

Of course, then there's their disgusting behavior. Nothing could excuse that.

I'd think so. Not a single line of cocaine in sight

@vintprox Please elaborate? To quote from the YAML spec: "every JSON file is also a valid YAML file".

Isn't YAML a superset of JSON?

@iiii only if you write the date as Y.M.D, which I haven't encountered yet. And even then, ISO is almost the same length, its standardized and sorts nicely in a purely lexicographic sort too

AFAIK, when using dots with numerical sorting, windows will sort each component indiviually. So 2.2 = 2.02. Not that it makes any sense.

For your array indexing example: you can write the same code in Rust. All you have to do is cast the bool to usize afterwards using as.

Today I accidentally muted the whole group call by focusing the wrong window. Mistakes like this happen. Change your root password and learn from the mistake

@iiii Probably, because the OCR vendor prints the PDF before running it through a scanner which performs OCR

Did you try surf? https://surf.suckless.org/

XCode?

What technology are you referring to?

If the class is defined in "lorum.cpp", you should add the new class to that file as well. Otherwise you would have to include the cpp file into the other file, which is considered bad practice.

No, not really. A finally clause is always executed, even if an exception is not handled in a catch clause. The code after the try would not be executed in that case.

@theabbie yes, that's him. Actually, the quote is from an xkcd strip: http://xkcd.com/196