3 ms·
See http://lambda-the-ultimate.org/node/4862 http://lambda-the-ultimate.org/node/4862.
by spicyj 13y ago
See http://lambda-the-ultimate.org/node/4862 http://lambda-the-ultimate.org/node/4862.
- z3phyr 13y agoThere will be a microsoft counterpart. There is a google counterpart. There is D. There is Parasail. There is Rust. There is Ada. All will fight out.... C++ will thrive under the patronage of its father, C
- stormbrew 13y agoSome patronage. I'm not sure any coding community is as hostile towards another as C's is to C++.
- MichaelGG 13y agoHmm interesting. The first thing they mention is GC. IMO that's very solvable with manual intervention, and probably not too hard to solve with tooling. A call a simple as String.Split can require allocating multiple objects on the heap just to make the call. (An array to string objects.) There's no reason this couldn't be stack-allocated. Similarly, there's probably lots of code that'd benefit from a pool allocation, like say, processing an HTTP request, where GC can be done just by freeing the pool.