lz | Functional utilities

A segmentation fault happens when the code try to access a memory region that is not available.

Accessing an array out of bounds doesn't means that the memory before or after the area occupied by the array is not available: The compiler or the runtime usually put all varibales or data in general in a given block of memory. If your array is the last item of such a memory block, the accessing it with a to big index will produce a Segmentaion Fault but is the array is in the middle of the memory block, you will just access memory used for other data, giving unexpected result and undefined behavior.

If the array (In may example, but valid for anything) is written, accessing available memory will not produce a segmentation fault but will overwrite something else. It may produce unexpected results or crash or segmentation fault later! This kind of bug is frequently very difficult to find because the unexpected result/behavior looks completely independent of the root cause.

Your object file recipes don't have any dependencies associated with them, so they won't get built unless you specify them explicitly.

Add the .c files to the dependency lists:

Problem solved by removing all nuget packages and reinstall it manual.

Seems compiler is not able to find the file in the includes path you mentioned.
First check if zconf.h file is available on your machine and get that location. If the file is available then just give the path of the file to the compiler using -I option.

Where does the initial state that you want to compress come from? I guess there are three likely options.

1. It's random. Most likely that means some code seeded a pseudo random number generator using some value like e.g. the time of the day, then used that to produce the values. In this case, you could get your hands on the seed (which most likely would be a fairly short number) and use that as the identifier from which everything else is computed. Make sure to use a portable random number generator with well-defined deterministic behaviour, e.g. some Mersenne Twister implementation. The JavaScript built in number generator is implementation-defined so it does not fit this bill.

2. It came from some catalog made by the game developer (i.e. you). Then just obfuscating the index into that catalog might be good enough.

3. It came from some user hand-tuning the values. In this case you're out of luck, since as I understand the problem chances are that any possible combination could get entered. You can't compress a large set of values to a smaller set of values without losing information.

There might be middle grounds. You could have a randomised setup that subsequently got hand-tuned, and the description as initial seed plus a few modifications would be shorter than the full set of settings. Or the hand-tuning would only be allowed following specific rules set out by the game developer, which again would make for a limited set of possible values and a potentially shorter encoding. Thinking along these categories might help you analyze your own situation and find a suitable solution.

You can also look at this from an information theory point of view. You can't expect to encode a sequence of fully independent and uniformly distributed digits with less information than those digits, perhaps expressed in some other base or whatever. You can compress data if there are patterns to it that make some combinations more likely than others. The more you tell us about these patterns, the better we might be able to advise. In total you can't get below the entropy of the source (i.e. game state distribution), so estimating that might help you find a lower bound for what to expect.

You can simply use Array#flatMap to flatten the dataReq array.

data.abc[0].dataReq = data.abc[0].dataReq.flatMap((d) => d);

The basic problem is that there are no backslashes in your string. Your source code has backslashes, but they are all escape signals. If you want to retain the backslashes in "WYSIWYG" style, use raw string mode:

-msse2 is the specific option, so passing that to GCC will work, if you get your build scripts set up to actually do that. https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html#x86-Options

Or better, use -march=native to enable everything your CPU has, if you're building for local use, not for distributing a binary that might have to work on an old-but-not-ancient CPU. (Of course, if you care about performance, it's weird to be building for 32-bit mode. SSE2 is baseline for x86-64. Unless your CPU is too old to support SSE2, e.g. a Pentium III. Or for example, there are embedded x86 CPUs without SSE, like AMD Geode. In that case, a binary built (successfully) with -msse2 will probably crash with an illegal instruction on such a CPU.)

-mfpmath=sse just tells GCC to use SSE for scalar FP math assuming that SSE is available; unrelated to telling GCC to assume the target CPU does support SSE2. It can be good to use it as well for performance, but it's not going to matter in getting your code to compile.

And yes, SSE1/2 intrinsic types like __m128i will only get defined when SSE is enabled, so error: ‘__m128i’ does not name a type is a clear sign that -msse wasn't enabled

This answer is for everyone, who wants to install powerline only in vim in the windows terminal (using wsl Ubuntu 20.04). It took me quite some time.

The reason why I had this issue was that glyphs where missing in the windows terminal font. I tried to install the powerline fonts according to the documentation(https://powerline.readthedocs.io/en/latest/installation/linux.html#fontconfig) as @romainl suggested but that didn't work. Furthermore I tried to install all powerline fonts from the github(https://github.com/powerline/fonts), I ran both the installation scripts. The one for windows in the powershell console according to this blog() and the one for Linux on the Ubuntu WSL Machine according to the documentation. Didn't work either. Then I stumbled upon a blog post of Microsoft(https://docs.microsoft.com/en-us/windows/terminal/tutorials/powerline-setup), where the person installed a theming framework oh-my-posh. However, I neither wanted to install a theming framework nor a special version of git. Furthermore I only wanted to install powerline in vim not in my whole console. This was the moment when I asked myself: did I miss something? And indeed I did catch a little detail. The answer was to install a the Cascadia Mono PL font (https://github.com/microsoft/cascadia-code/releases) which includes the missing glyphs. Just download the zip and double click on the font. Furthermore I had to set the fontface in the setting.json of the windows terminal (which can open with pressing (CTRL + ,) in the terminal). Your settings should look something like this: