legal | Boilerplate legal templates for startups in Singapore

I have this dataframe DF:

As I understand, when compiling a compilation unit, the compiler's preprocessor translates #include directives by expanding the contents of the header file¹ specified between the < and > (or ") tokens into the current compilation unit.

It is also my understanding, that most compilers support the #pragma once directive guarding against multiply defined symbols as a result of multiple inclusion of the same header. The same effect can be produced by following the include guard idiom.

My question is two-fold:

1. Is it legal for a compiler to completely ignore an #include directive if it has previously encountered a #pragma once directive or include guard pattern in this header?
2. Specifically with Microsoft' compiler is there any difference in this regard whether a header contains a #pragma once directive or an include guard pattern? The documentation suggests that they are handled the same, though some user feels very strongly that I am wrong, so I am confused and want clarification.

¹ I'm glossing over the fact, that headers need not necessarily be files altogether.

Problem

I have a large JSON file (~700.000 lines, 1.2GB filesize) containing twitter data that I need to preprocess for data and network analysis. During the data collection an error happend: Instead of using " as a seperator ' was used. As this does not conform with the JSON standard, the file can not be processed by R or Python.

Information about the dataset: Every about 500 lines start with meta info + meta information for the users, etc. then there are the tweets in json (order of fields not stable) starting with a space, one tweet per line.

This is what I tried so far:

1. A simple data.replace('\'', '\"') is not possible, as the "text" fields contain tweets which may contain ' or " themselves.
2. Using regex, I was able to catch some of the instances, but it does not catch everything: re.compile(r'"[^"]*"(*SKIP)(*FAIL)|\'')
3. Using literal.eval(data) from the ast package also throws an error.

As the order of the fields and the legth for each field is not stable I am stuck on how to reformat that file in order to conform to JSON.

Normal sample line of the data (for this options one and two would work, but note that the tweets are also in non-english languages, which use " or ' in their tweets):

When creating a new node in a linked list, is it legal to use designated initializers to initialize the members of the node as mentioned below? Is there any repercussion in doing so and what would be a better way to achieve the same result? (lang : C++)

I'm trying to store data into a database and I encountered a situation where I don't know is it feasible or not to do that.

so I have two following tables in the database

After instantiating a 2D convolution with conv = nn.Conv2d(8, 8, 3, bias=False), whose member bias should be None, is it able to give conv a legal bias again (whether with random initialization or determined values)?

I observed that bias in other default convolution modules is of the type Parameter, so I suspect there are extra procedures beyond simply conv.bias = torch.tensor(...) to make the new bias legal for conv.

I'm writing a program to detect if there are ones in the even bits. 0101 has ones in the even places for example. And this solution happens to work but I have no idea why.

What confuses me is that when we shift 16 bits to the right. For example with 0101 we're just creating 0000 0000 0000 0000 0101 right? Then we do an and with the original number so it'd be 0000 0000 0000 0000 0101 & 0000 0000 0000 0000 0101 is just the same number right? So if we do this shifting over and over and eventually x&1 I don't see how this helps anything to return 1 if allEvenbits.

The code below was working fine, and then it suddenly started sending corrupted PDF attachments.

I have been self-learning TypeScript via the TS docs. While reading a section that I posted below, (in text form, as well as the link), I came across a word I haven't heard before ARITY. Usually I just search the TS docs to find out what some specific syntax means, but I am guessing this isn't TypeScript, because the docs didn't return any specific definition for 'Arity' in the search Results. As stated above, below is the documentation I came across, that uses 'Arity'. The documentation relies on heavily on the definition of 'arity', and I couldn't find anyone defining it here on stackoverflow, or in a DDG search. If anyone could define this for me that would be awesome.