Concepts are already here - (as of now) they fix a subset of this, and errors messages can still be extremely long.
They’re less like “here’s every single template parameter of the involved types” and more like “this template thingy has many specializations with different constraints, here’s a list of all of them and why none of them are satisfied with your parameters”
Not evil by itself, but if you want to obfuscate C++20 code you can get REALLY creative…
C++, lawful good
Who wouldn’t pity those who make do with a lossy compression image format?
My personal minimum is a stable 40/s, which is roughly where I start noticing the lower framerate without paying attention to it.
With 30/s I need to get used to it, and I usually underclock (or, rather, power-limit) my GPU to hit an average 50 unless the game in question is either highly unstable (e.g. Helldivers 2) or the game is so light I don’t have to care (e.g. Selaco).
Lua - Portuguese feminine noun for “moon”, coming from the Latin “luna”
Luna - Latin, feminine noun (coincidentally identical to the Italian noun, also feminine)
Yup, Lua is a girl.
I’m pretty sure the .file notation is a bug-turned-feature of a GNU coreutils program, Windows has no such thing and marks files as hidden using filesystem attributes.
I couldn’t say whether I prefer it one way or the other, but the dot prefix does stick out like a sore thumb on systems that don’t hide them by default… though I think AnyOldName3’s explaination makes sense.
Everyone here is talking about conventions used on Linux, but this looks like Windows Explorer to me…?
Why are there so many directory names in there following Linux “hidden file” conventions, if that’s the case?
VS Codium did that at some point, it probably still does but I haven’t checked
Chromehounds, trying to squeeze as much nostalgia fun out of it to compensate not having been able to play more than three times online (as the game was intended).
Just tested this: the “original+” code compiles, but does not increment i.
There were two problems:
b(bool) and b(char) are ambiguous (quick fix: change the signatures to char b(bool&) and auto b(char&& v));b functions, even if the constraint is only checked after both, I was unaware of this (fix: define C immediately before void inc(int&)).It’s funny that it complains about all of the right stuff (except the ‘int’ thing), but it doesn’t say anything about the concept.
About the ‘int’ literal (which is not a string): cppreference.com has a description on this page about it, ctrl+f “multicharacter literal”.
Just surround your eyes with try { … } catch(Up& up) { }, easy fix
Multiple-character char literals evaluate as int, with implementation defined values - it is extremely unreliable, but that particular piece of code should work.
// C++20
#include <concepts>
#include <cstdint>
template <typename T>
concept C = requires (T t) { { b(t) } -> std::same_as<int>; };
char b(bool v) { return char(uintmax_t(v) % 5); }
#define Int jnt=i
auto b(char v) { return 'int'; }
// this increments i:
void inc(int& i) {
auto Int == 1;
using c = decltype(b(jnt));
// edited mistake here: c is a type, not a value
// i += decltype(jnt)(C<decltype(b(c))>);
i += decltype(jnt)(C<decltype(b(c(1)))>);
}
I’m not quite sure it compiles, I wrote this on my phone and with the sheer amount of landmines here making a mistake is almost inevitable.
No, all files are base 256
Isn’t auto a keyword in C?
Types being declarable as virtual members is something I want to never hear again
Relatable tbh