Python cryptography, Rust, and Gentoo [LWN.net]

Python cryptography, Rust, and Gentoo

Posted Feb 12, 2021 17:56 UTC (Fri) by khim (subscriber, #9252)
In reply to: Python cryptography, Rust, and Gentoo by mathstuf
Parent article: Python cryptography, Rust, and Gentoo

The things which you have listed are not larger than what Rust gets in three years, though.

Small additions like these are added rust basically every release.

But concepts and especially modules… they change things. Not just allow you to write less code in some cases, but allow you to do things which weren't possible (or a least weren't feasible) before on the level of them whole program design.

Even metaprogramming doesn't change C++ as much as modules or concepts: you just get “for free” something which was already available before — just with IDL and tools like capnproto.

Sure that's nice simplification, but it doesn't imply insane amount of work which would be needed to make modules or concepts work. They would require changes in literally everything: from standard library to third-party libraries and many other things before they would become truly useful.

All the things that you listed are, actually, pretty minor in comparison: they only need local changes for you to benefit from them.

to post comments

Python cryptography, Rust, and Gentoo

Posted Feb 12, 2021 18:41 UTC (Fri) by mathstuf (subscriber, #69389) [Link]

> The things which you have listed are not larger than what Rust gets in three years, though.

Maybe not. These are not things that I think any one person's view is going to give the same size and scope for any individual feature as another's view anyways. Personally, these are not "small" things to be adding to C++ (in aggregate).

Pattern matching, at least, adds a decent amount of syntax to the language. Contracts does too (though, thankfully, both are via context-sensitive keywords). Template-this also has some additional syntax (though that feels like a cleanup at least).

Modularized stdlib probably is going to have knock-on effects for projects not using IWYU where types aren't leaking out over entire #include trees.

I'm also aware of the scope of modules pretty intimately: I'm working with the ISO committee to make sure they can be built at all :) .