The idea that a general purpose programming language designed for portability and efficiency should map directly to your favourite machine architecture (thus the implementation of it on any other being a virtual machine of said architecture) is both relatable and delusionally egocentric.
what we say to save our skin: a garbage collector is more efficient than smart pointers in real world projects.
what we actually mean: if you want to write spaghetti code, with smart pointers you'll hit a brick wall pretty fast, while a garbage collector will delay this face flattening experience long enough for you to abandon ship.
the absolute state of #programming
also not a fan of these pure code specs in the standard (apply and make_from_tuple), spelling it all out in english they probably would've avoided these weird inconsistencies... reminds me of some video codec specs, where it feels like they just copy pasted the implementation: "there ya go, cryptic c code, that's your spec"...
so whether tuple_cat works with tuple-like types is implementation defined,
apply doesn't work with them period (except standard tuple-likes),
and make_from_tuple apparently is like apply in c++17, but is supposed to work with them in c++20, and yet no implementation complies... I must know who is responsible for this! some pussy ass library vendor no doubt >:(
old code new question: can you spot the undefined behaviour? omg! and how can I ever recover from this?
In order to not care about efficiency, the abstractions must be efficient. Otherwise the care is still taken, except in the most backwards ways.
Array indices correspond to meaningful positions, not elements. Array of N elements has N+1 meaningful positions. Array[i] is not the ith element of an array, it's the element ahead of the position that is i units ahead of the first meaningful position (or behind the position that is i units behind the last meaningful position). This is why we start at 0, just like on a number line. Nobody counts from 0.
Don't you love it when your fresh baked gui designed to handle any screen size and dpi breaks, cause the underlying system changes the meaning of a pixel, so that some old fart application that didn't care scales?
- Why don't you just go fix the old farts?
- We can't they proprietary ToT, here is some backwards API you can juggle to get back to sanity ^_^
Is this the posting - window?
Hi I'm new here and want to present you the first realisation of the bKeplerian Music of the Spheres. So lets try:
https://video.qoto.org/videos/watch/b6532f88-c934-4dfd-a71b-0d0df2bc9724
Is the object empty? Neither javascript nor lua know...
meanwhile:
https://en.cppreference.com/w/cpp/types/is_empty
https://en.cppreference.com/w/cpp/iterator/empty
Pesky misleading semicolon like this just cost me a couple of hours of going absolutely insanely bonkers crazy (in another language): http://ix.io/2Lu3
Very glad that gcc is actively ruining this guy's whole career.
Also something in this paste is breaking ix.io's html syntax highlighting. It turns <iostream> into an html tag:
http://ix.io/2Lu3/cpp
Wonderful.
open.tube "censorship free youtube alternative" deleted my channel for no reason and made all the links i shared redirect to a violent video
open.tube "censorship free youtube alternative" deleted my channel for no reason and made all the links i shared redirect to a violent video