Thales Fragoso

typ

Natural languages are incredible informal and ambiguous.

From the people who brought you "Free Monads" comes a new challenge: Freer Monads.

Mutable alias with references is UB. It's basically the textbook use of unsafe.

Does it really need to be safe though?

I would rather have it marked unsafe with proper `Safety` comments than have it "safe, but not really".

Ok, you got me worried for a sec.

Did bluesky just pulled a link preview from your spelled-out url?

Who decides which parts are the goodies and which aren't?

As vezes faltam as metas concretas também.

I'm currently using choc sunsets, a bit more difficult to find but I'm really liking them.

Mas precisa disso tudo? A proteção vale pra criatura também? Minha interpretação era que só protege o jogador.

Can you give an example of the last sentence?

Pra deixar claro, interpretei "o mexe quase nada em documentação" como mudanças pequenas/insignificantes na documentação.

Mas agora não tenho certeza se interpretei certo .-.

"LGTM, thanks." (Clicks merge).

Sou preguiçoso, qualquer outra coisa seria esforço sem benefício.

Também comecei no Malboro depois de aprender python.

rustls already covers a good chunk of openssl use cases.

It doesn't do its own crypto however, but that isn't necessarily bad. People usually roll with assembly for that still anyways.

You might even be able to do with references and safe code, but the resulting type won't be very flexible to use, since it will be borrowed for the whole time it exists. You might be interested in reading:

doc.rust-lang.org/nomicon/drop...

You can do with raw pointers and care. Also, you probably want to pin `xs` before creating the pointers because a lot of methods in Vec can invalidate its original memory.

I use async even for stupid CLI tools. Easily selecting concurrency abstractions is a game changer.

Do you mean that they end up erasing the underlying type even if they don't need to?

@sseraphini.bsky.social isso é verdade?

All is good until you accidentally convert a concrete error to an error interface.

In which way go is more type-safe than C#? Genuine question.

People say that allocations never fail on linux, and that it kills your process instead.

Weird question, but which OS?

Concordo com o conselho na situação que foi dado.

Mas com o tempo é sempre bom tentar achar um equilíbrio.

"Na indústria" é comum que o "sempre pode melhorar depois" seja uma grande ilusão.

"OO is about hardend boundaries, self containment, modeling the problem domain, &c."

That just sounds like any other abstraction. Can you be more precise on what OOP in specific brings to the table?

Just be careful to not accidentally convert the value to an error interface. That might take a bit to debug...

Tá com a mulesta.

An example would be using it with any type that might have padding.

My recommendation is to use crates that already have that thought out, like zerocopy or bytemuck.