Is this how you do Fin in peasant languages?
Programmer Humor
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
No, not at all. It's a joke post, abusing the in-memory representation of the Option
type to construct numbers. When nesting the Option
type, it turns into a densely packed bit vector...
And if I understand the purpose of Fin
correctly, you're picking on the one 'peasant language' that actually has something like that built-in.
In Rust, you can specify the type of an array as e.g [u8; 3]
. Which is an array containing values of type u8
(unsigned 8-bit integer) with a fixed, compile-time-guaranteed length of 3
. So, [u8; 3]
could be used to represent an RGB color, for example.
It is an array, not a set, but well, close enough.
If you think that's good, then you're gonna love this "simplified" real code posted as a real issue on one of my Github repos.
Edit: updated link to address the stack-trace comment
That's not actual code though, it looks like some kind of trace. Notice the filenames at the end of each line.
The actual solution the issue opener there might be looking for is to disable C++ parsing, since it's not actually C++ code, it's just some text they pasted into VSCode and they're wondering why their editor can't handle it.