Skill issue

- sincerely, someone making a DST crate

EDIT: To clarify…

There are some things that are only doable on nightly Rust (like specialization, const fn in traits, etc.) and the reason for that is to avoid future issues. In that regard, Rust will not be as good as C++… at least until those get stabilized.

Some of the nightly functionality (like ptr_metadata) can be achieved with unsafe code and it’s fine to do that, as long as it’s only done when necessary and it’s properly documented.

It’s okay to want to use C++, but that language has it’s own issues and footguns (virtual destructors, “move semantics”, C-style casts, header files and more) that Rust wants to avoid.

EDIT 2: Specialization is also kinda doable with deref coercion, but that’s another can of worms I don’t wanna open here.

EDIT 3: And if I had to mention some of Rust’s footguns:

• unwrap panics, which isn’t bad in and of itself, but it’s short so you’ll probably want to use it instead of other error handling methods (see recent Cloudflare outages)
• unsafe functions implicitly allows using unsafe operations (fixable by adding #! [deny(unsafe_op_in_unsafe_fn)])

:3

Might as well…

Aaaaand of course it’s Polskie Stronnictwo Lobbyingowe

Oh :(

Okay. It’s gone now.

good argument. unfortunately i don’t care

deleted by creator

I’ve seen this before. Is this a translation?

AI - another indian

Yeah, I know. I didn’t notice. Sorry.

Shizuku?

EDIT: I didn’t notice it was mentioned already. XDD

Not for long :'(

Cool bug Fact is

Is the title the issue? Should I change it and to what?

The point is - GitHub has a spam issue. The perpetrators created multiple issues per minute, atting multiple users and added a misleading url to the issue content.

GitHub could have done something to prevent that.

I don’t get it either