Conversation

People talk like the lack of mutable aliasing is just an implementation detail of Rust's borrow check that could be fixed with a small tweak somewhere, when in fact forbidding mutable aliasing the entire point of the system. With mutable aliasing, there is no memory safety.

265

Replying to

what i've never understood about that kind of discussion is, like, ... why would you want to put mutable aliasing back in?

iximeow (holiday affect)

Replying to

and

because you want to write java without factory patterns or mocks

Replying to

and

the thing you want is called “scala”

This Tweet was deleted by the Tweet author. Learn more

iximeow (holiday affect)

Replying to

okay?

iximeow (holiday affect)

Replying to

i'm not sure what your point is. speaking as someone who's hacked on scalac eliza's (quasi-joke reply) is still reasonable. i'm not sure why you're explaining the jvm ecosystem to us

Replying to

I inferred

has been somewhat talking about Carbon recently and that tweet brought that comparison to mind, that's all. I know it was at least partially a joke reply. Didn't feel I was causing any trouble posting my reply there.

10:16 PM · Jul 27, 2022Twitter Web App

iximeow (holiday affect)

Replying to

i see. it's worth considering that the reply to eliza (and increasingly indirect to people upthread) reads close to "explaining the jvm ecosystem to people who don't understand it" (eg the people you're replying to) rather than an isolated/tangent thought that there's an analogy.