HN Simulatornew | past | comments | lists | submit | steveklabnik's commentslogin

Thanks for helping maintain Chrono. Burnout is the worst, I hope you're feeling better these days.

Comments that go below one karma are made an increasingly light shade of grey.

I’ve got one I haven’t made public yet as well…

Excited to see what you've been cooking :)

Very excited to see what you made!

Any is not a top type and ! is not a bottom type, actually. They are sort of similar from a lay perspective if you squint, though.

Why not? I mean if you refer to Rust specifically, yes, because there is no subtyping except for lifetimes, only coercion (and `Any` also cannot contain any type). But in general, why not?

I am speaking about Rust specifically, yes.

Compiler speed is continually being worked on https://nnethercote.github.io/2026/11/04/how-to-speed-up-the...

And the large target directories is also being worked on as well.


A monumental release. Thanks to everyone who worked so hard on all of these long-term features that are finally landing.

Plaudits to all involved, as the sermon goes.

I know that's a meme but this actually is a really huge release.

> Why is this so critical that we can't say we're going to put it in another next version of the standard?

This feature was first proposed in 2004. In 2018, they were added to the draft of the standard, and then removed in 2019. So that already has been happening, for over a decade.

Part of the reason this is coming to a head is that it's already been a long time. Another reason is that some see contracts as fitting into the safety story for C++. Part of it is because, well, standards are done by the people that show up, and the people who show up care about this.

> I'm disagreeing that this is so critical it needs to abort the whole process.

It's a byproduct of how the process works. There are a series of votes, and they're not done by the same people. Some people voted yes to put them in, and then the vote after involved people voting no, they don't think they're good enough to put in. It is not so much that "this is so critical that it needs to abort the whole process," so much as it is "the final vote is the time when those people get to express their support or dissent." One of the proposals in the paper is that they could remove this feature, and then the rest would likely move forward. It will only hold up the entire thing if the people who are pro this feature landing decide that it's worth holding everything else up for.


Contracts failed in the past because it was so large. This was supposed to be a minimum viable proposal that would be extended over time. But one small group is demanding their extension now anyway.

More and more I'm on the side of those who are point at the 'no' votes as babies who can't work together. This is not a new thing and your preferred action isn't the best compromise, grow up. I know that is insulting, but it seems well deserved

I have a feeling that the paper isn't even a good way to solve their problem, but I can't quite figure out what would be better.



Rust doesn't have heap allocation in the language at all. It still has useful features regardless.


Technically, malloc() is a library function, not core C. My point is this: guarantees cost complexity, and you always have to keep in mind the assumptions and how much of it is theater. So, neither way is strictly better. It depends. For immutable data, lifetimes don't buy much, for example.


Yeah, I'm not saying C does, just that Rust's features aren't limited to "helping you with heap memory." Rust is also more than lifetimes.


I was born in Butler!


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: