affenape

5 ms·

1.
by affenape 14d ago
It did for sure, but the problem with C++ is its heritage, specifically that structures can be self-referential. For instance, the Rust's url::Url type has to use usize offsets for tracking the location of each of its components. Conve
2.
by affenape 2mo ago
I've tried using RustRover over WSL2 multiple times with every new release, but it's been a huge disappointment every time. My fans constantly spin like crazy, memory vanishes into thin air, and typing is super laggy - it even ove
3.
by affenape 6mo ago
From the proposal, I see a bunch of new keywords and rules - alright given the language's heritage. But what happens if I "relocate" a variable value - would a "shell" remain or how exactly C++ is supposed to handle
4.
by affenape 6mo ago
Finally, reflection has arrived, five years after I last touched a line in c++. I wonder how long would it take the committee, if ever, to introduce destructing move.
5.
by affenape 6mo ago
Not necessarily. A coroutine encapsulates the entire state machine, which might pe a PITA to implement otherwise. Say, if I have a stateful network connection, that requires initialization and periodic encryption secret renewal, a coroutine
6.
by affenape 10mo ago
> A %PRODUCTNAME% next generation editor/ide is released > Look inside > VS Code
7.
by affenape 1y ago
Can it run doom? Can it make doom come true?
8.
by affenape 1y ago
For something having 2024 in its name I expected a more consistent error handling, but guess what: * some functions like fsRenderCreate return 0 or 1 depending on the operation result; * some like fsMapViewCreate say that a value less than
9.
by affenape 1y ago
Yikes... everything looks like jelly. Best served with Comic Sans MS.
10.
by affenape 2y ago
Would be really NICE.